All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: FETCH_HEAD files and mirrored repos
Date: Mon, 13 Jul 2020 21:11:48 -0700	[thread overview]
Message-ID: <20200714041148.GB2208896@google.com> (raw)
In-Reply-To: <79a56e7b-3c31-80c0-6a8b-807dcb4d5af3@kdbg.org>

Johannes Sixt wrote:
> 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.

Speaking for myself as a user, I also rely on (the first line of)
FETCH_HEAD being written so that I can run commands like "git log
FETCH_HEAD".  What I don't rely on is the massive amounts of data that
may get written after that first line.

Thanks,
Jonathan

      parent reply	other threads:[~2020-07-14  4:11 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               ` FETCH_HEAD files and mirrored repos Konstantin Ryabitsev
2020-07-13 20:04                 ` 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 [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

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

  git send-email \
    --in-reply-to=20200714041148.GB2208896@google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.