git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: `git fetch` not updating 'origin/HEAD' after branch rename

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 13, 2021, 21:22 UTC
Message-ID
<xmqqzgy1khgb.fsf@gitster.g>
In-Reply-To
<87pmyxc2n3.fsf@igel.home>
Andreas Schwab <schwab@linux-m68k.org> writes:
Show 9 quoted lines
> On Apr 13 2021, Junio C Hamano wrote:
>
>> It may also be
>> possible to add "git fetch --reset-remote-tracking-HEAD" option to
>> make "fetch" overwrite existing origin/HEAD but somebody has to
>> propose such a change, argue for its benefit and get it accepted by
>> the community.
>
> Isn't that what git remote set-head origin -a does?

Yes, but the point is to do so when fetch is run (i.e. it talks with the other side not just to learn which branch their HEAD points at, but it actually does the fetching of new history on branches). And it might open the door to add a configuration to tell "fetch" to do so unconditionally, if it turns out to be useful enough.

Previous: Andreas SchwabNext: Chris Torek
Message 4 of 10 in “`git fetch` not updating 'origin/HEAD' after branch rename”
  1. Sam BostockApr 13, 2021
  2. Junio C HamanoApr 13, 2021
  3. Andreas SchwabApr 13, 2021
  4. Junio C HamanoApr 13, 2021
  5. Chris TorekApr 14, 2021
  6. Jeff KingApr 14, 2021
  7. Ævar Arnfjörð BjarmasonApr 14, 2021
  8. Andreas SchwabApr 14, 2021
  9. Junio C HamanoApr 14, 2021
  10. Jeff KingApr 15, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.