From: Eric Wong <e@80x24.org>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: meta@public-inbox.org
Subject: Re: How to initialize Git repos
Date: Fri, 29 Mar 2024 20:18:20 +0000 [thread overview]
Message-ID: <20240329201820.M667212@dcvr> (raw)
In-Reply-To: <87edbv3jtc.fsf@lease-up.com>
Felix Lechner <felix.lechner@lease-up.com> wrote:
> Hi,
>
> When I edit the config file manually, i.e. without public-inbox-init,
You can still use -init, it should be idempotent
> I see errors until messages are added, such as:
>
> ($INBOX_DIR/description missing)
for v1, it's the same as $GIT_DIR/description gitweb uses.
for v2 it's the same thing at the top-level (same level as all.git)
> or
> fatal: not a git repository (or any parent up to mount point /srv)
> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
> error in git rev-parse --git-dir (cwd:.):
>
> How may I initialize a new Git repo before adding any messages, please?
Not sure, v1 should just be a bare git repo (git init --bare).
prev parent reply other threads:[~2024-03-29 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 13:06 How to initialize Git repos Felix Lechner
2024-03-29 20:18 ` Eric Wong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240329201820.M667212@dcvr \
--to=e@80x24.org \
--cc=felix.lechner@lease-up.com \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).