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

Re: [Non-Bug] cloning a repository with a default MASTER branch tries to check out the master branch

From
Junio C Hamano <gitster@pobox.com>
Date
May 27, 2017, 23:55 UTC
Message-ID
<xmqqh905c0tm.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CEF93B59EA3F49608B41892952454B1D@PhilipOakley>
"Philip Oakley" <philipoakley@iee.org> writes:
Show 5 quoted lines
> However given the discussion about an unborn HEAD, the option here
> would be to also pass the NULL sha for the symref and then add the
> annotation 'HEAD' after an extra \0, in the same way that an active
> symref could be annotated with the '\0HEAD'. This would kill two birds
> with one stone!

Are you aware of the symref capability that is already advertised in the initial upload-pack response? Right now, we do so only when HEAD actually points at something, and the earlier suggestion by Peff is to do so unconditionally, even when HEAD is dangling.

Existing clients that are symref aware do not do anything (good or bad) when a HEAD that is dangling [*1*] is advertised, so such a change will not hurt (but it would not help by itself either). Ancient clients that are not even aware of the symref are not affected.

Then new clients _could_ start paying attention to the advertised HEAD that is dangling.

The bundle transport is a different beast. I do not think it advertises where HEAD is pointing at, whether it is dangling or not.

[Footnote]
*1* A HEAD symref that is advertised in the upload-pack response is
    dangling when its pointee does not appear in the set of refs
    that are advertised.  Félix's case would have shown HEAD
    pointing at refs/heads/master in the symref capability extension,
    but the list of refs and their values would not have included
    that ref (there was only refs/heads/MASTER "for joke reasons").
Previous: Philip OakleyNext: Philip Oakley
Message 12 of 17 in “[Bug] cloning a repository with a default MASTER branch tries to check out the master branch”
  1. Félix SaparelliMay 22, 2017
  2. Junio C HamanoMay 23, 2017
  3. Philip OakleyMay 23, 2017
  4. Jeff KingMay 24, 2017
  5. Junio C HamanoMay 25, 2017
  6. Junio C HamanoMay 25, 2017
  7. Jeff KingMay 25, 2017
  8. Jeff KingMay 25, 2017
  9. Junio C HamanoMay 25, 2017
  10. Philip OakleyMay 26, 2017
  11. Philip OakleyMay 26, 2017
  12. Junio C HamanoMay 27, 2017
  13. Philip OakleyMay 28, 2017
  14. Junio C HamanoMay 28, 2017
  15. Jeff KingMay 31, 2017
  16. Samuel LijinMay 23, 2017
  17. Jeff KingMay 23, 2017

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.