On Mon, Jul 13, 2020 at 10:13:28AM -0700, Junio C Hamano wrote: > > 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. Does it make sense to add logic for whether this is done in a bare repo? I can't imagine common cases where a FETCH_HEAD would be useful outside of a checkout where a merge is likely to happen. -K
