From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] lei_mirror: unlink FETCH_HEAD when fetching forkgroups
Date: Wed, 8 Mar 2023 14:31:53 -0500 [thread overview]
Message-ID: <20230308193153.hcx6jl727e5t7cwj@nitro.local> (raw)
In-Reply-To: <20230308110258.525501-1-e@80x24.org>
On Wed, Mar 08, 2023 at 11:02:58AM +0000, Eric Wong wrote:
> Apparently, --no-write-fetch-head is broken in current git[1].
> It also wasn't in older git, at all. So just unlink FETCH_HEAD
> as we see it, but keep using --no-write-fetch-head to avoid the
> syscall and I/O overhead when we can.
I'm pretty sure --no-write-fetch-head was added in response to me asking why
it's needed for bare repos in the first place. In grokmirror, we symlink it to
/dev/null, but you already know this probably.
-K
prev parent reply other threads:[~2023-03-08 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 11:02 [PATCH] lei_mirror: unlink FETCH_HEAD when fetching forkgroups Eric Wong
2023-03-08 19:31 ` Konstantin Ryabitsev [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=20230308193153.hcx6jl727e5t7cwj@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--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).