git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Chris Torek" <chris.torek@gmail.com>,
	"Sam Bostock" <sam.bostock@shopify.com>,
	"Git List" <git@vger.kernel.org>
Subject: Re: `git fetch` not updating 'origin/HEAD' after branch rename
Date: Wed, 14 Apr 2021 14:12:57 -0700	[thread overview]
Message-ID: <xmqqim4oy3hi.fsf@gitster.g> (raw)
In-Reply-To: <87pmyxjcnz.fsf@igel.home> (Andreas Schwab's message of "Wed, 14 Apr 2021 14:03:44 +0200")

Andreas Schwab <schwab@linux-m68k.org> writes:

> On Apr 14 2021, Ævar Arnfjörð Bjarmason wrote:
>
>> Nothing in git itself actually needs this remote HEAD past clone time,
>> and with 4f37d457065 (clone: respect remote unborn HEAD, 2021-02-05)
>> there'll be even less reason to pay attention to it.
>
> Isn't that what git rev-parse origin resolves to?

Correct.

And that is why refs/remotes/origin/HEAD is defined to point at the
branch that the owner of LOCAL repository considers is of interest,
which may not be the same as what the owner of the REMOTE repository
thinks is the primary branch in their worldview.



  reply	other threads:[~2021-04-14 21:14 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
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 [this message]
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=xmqqim4oy3hi.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=chris.torek@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sam.bostock@shopify.com \
    --cc=schwab@linux-m68k.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. 
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).