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

Re: Change default branch name (server side) while cloning a repository

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Mar 27, 2015, 16:40 UTC
Message-ID
<vpqmw2ytmuk.fsf@anie.imag.fr>
In-Reply-To
<1427459241861-7627964.post@n2.nabble.com>
Garbageyard <varuag.chhabra@gmail.com> writes:
Show 6 quoted lines
> If i now clone the repository on my local machine, then the default branch
> should be pointing to mainline and not master. However, the issue is that it
> still points to master. Am I /wrong/ in assuming that changing the entry in
> file HEAD for a given repository on Git server will change the default
> branch while cloning? If I’m wrong, can anyone please tell me how can I
> enforce this change on the /server/ side correctly?

IIRC, there's a known limitation of the Git protocol which does not transmit symbolic ref over the network. Only the HEAD's sha1 is transmitted and the client guesses which branch should be checked out based on this. But it can guess incorrectly if several branches point to the same commit.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Jeff King
Message 4 of 4 in “Change default branch name (server side) while cloning a repository”
  1. GarbageyardMar 27, 2015
  2. Stefan NäweMar 27, 2015
  3. Jeff KingMar 27, 2015
  4. Matthieu MoyMar 27, 2015

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.