From: Chris Torek <chris.torek@gmail.com>
To: Sam Bostock <sam.bostock@shopify.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: `git fetch` not updating 'origin/HEAD' after branch rename
Date: Tue, 13 Apr 2021 17:26:02 -0700 [thread overview]
Message-ID: <CAPx1GvdeNEyPEZ7GdRKeAevnvjyLmoXHjQP0W6iToDsJPAqDHA@mail.gmail.com> (raw)
In-Reply-To: <CAHwnEogvmTZ-VS5GksoGEiyo3EHO+At+xeWa3frXUESD3HicnQ@mail.gmail.com>
On Tue, Apr 13, 2021 at 5:18 PM Sam Bostock <sam.bostock@shopify.com> wrote:
> Long story short, it seems to me that `git fetch` should update
> "refs/remotes/origin/HEAD" when the upstream HEAD changes, but it
> doesn't.
It's never been the *intent* to have `git fetch` update
the corresponding remote-tracking `HEAD` ref. To make
that happen, you must run `git remote`:
git remote set-head origin -a
for instance.
I have, however, often thought that this is the wrong
*default* way for things to work, and that at least by default,
`git fetch origin` should update `origin/HEAD` if the
fetch result indicates that it should. See also Junio's
reply. I think a configuration knob (similar to `fetch.prune`)
would be reasonable here. Users could then be encouraged
to set `fetch.prune` to `true`, and `fetch.update-remote-HEAD`
(or whatever) to `true` as well.
Chris
next prev parent reply other threads:[~2021-04-14 0:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 20:25 `git fetch` not updating 'origin/HEAD' after branch rename Sam Bostock
2021-04-13 20:37 ` Junio C Hamano
2021-04-13 21:09 ` Andreas Schwab
2021-04-13 21:22 ` Junio C Hamano
2021-04-14 0:26 ` Chris Torek [this message]
2021-04-14 5:29 ` Jeff King
2021-04-14 10:56 ` Ævar Arnfjörð Bjarmason
2021-04-14 12:03 ` Andreas Schwab
2021-04-14 21:12 ` Junio C Hamano
2021-04-15 9:28 ` Jeff King
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPx1GvdeNEyPEZ7GdRKeAevnvjyLmoXHjQP0W6iToDsJPAqDHA@mail.gmail.com \
--to=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
--cc=sam.bostock@shopify.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).