Re: FETCH_HEAD files and mirrored repos
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 13, 2020, 17:13 UTC
- Message-ID
- <xmqqk0z7nxs7.fsf@gitster.c.googlers.com>
- In-Reply-To
- <79a56e7b-3c31-80c0-6a8b-807dcb4d5af3@kdbg.org>
Johannes Sixt <j6t@kdbg.org> writes:
Show 12 quoted lines
> Am 12.07.20 um 22:52 schrieb Junio C Hamano: >> We could teach "git fetch" a new "--write-fetch-head" option and >> teach "git pull" to pass it when calling "git fetch". It is very >> plausible that some folks rely on "git fetch" to leave FETCH_HEAD >> without being told, so the option must default to on for a few >> development cycles before we flip the default to off, > > Nah, really??? It's one of the benefits of git-fetch that it writes > FETCH_HEAD and the primary reason in many cases where I use the command! > So, either I don't care that FETCH_HEAD is written, or I do use it. IMO, > not wanting to write FETCH_HEAD is the odd case and would need a > configuration tweak, not the other way round.
Yeah, that's even easier to arrange.
Just the "--[no-]write-fetch-head" command line option and the fetch.writeFetchHEAD configuration variable are introduced and left off by default forever.