git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Sixt <j6t@kdbg.org>, git@vger.kernel.org
Subject: Re: FETCH_HEAD files and mirrored repos
Date: Mon, 13 Jul 2020 16:00:49 -0400	[thread overview]
Message-ID: <20200713200049.6a22nek4xckwtpt6@chatter.i7.local> (raw)
In-Reply-To: <xmqqk0z7nxs7.fsf@gitster.c.googlers.com>

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

  parent reply	other threads:[~2020-07-13 20:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 20:48 FETCH_HEAD files and mirrored repos Konstantin Ryabitsev
2020-07-11 21:07 ` Junio C Hamano
2020-07-11 21:19   ` Konstantin Ryabitsev
2020-07-12 17:33     ` Junio C Hamano
2020-07-12 20:25       ` Konstantin Ryabitsev
2020-07-12 20:52         ` Junio C Hamano
2020-07-12 21:54           ` Konstantin Ryabitsev
2020-07-13 17:09           ` Johannes Sixt
2020-07-13 17:13             ` Junio C Hamano
2020-07-13 18:06               ` [PATCH] fetch: optionally allow disabling FETCH_HEAD update Junio C Hamano
2020-07-13 19:08                 ` Taylor Blau
2020-07-13 19:45                   ` Junio C Hamano
2020-07-13 20:00               ` Konstantin Ryabitsev [this message]
2020-07-13 20:04                 ` FETCH_HEAD files and mirrored repos Junio C Hamano
2020-07-13 20:22                   ` Jeff King
2020-07-13 20:34                     ` Konstantin Ryabitsev
2020-07-13 20:50                       ` Jeff King
2020-07-13 20:43                     ` Johannes Sixt
2020-07-14  4:11             ` Jonathan Nieder

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200713200049.6a22nek4xckwtpt6@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.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 NNTP newsgroup(s).