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

Ambiguous branch names...

From
IRIngo Rohloff <lundril@gmx.de>
Date
Feb 16, 2014, 20:34 UTC
Message-ID
<20140216203439.GA15538@localhost>
Hello,
while trying out git (version 1.7.9.5), I did this:
git clone -- ssh://myserver/~rohloff/git/w1.git w1

So I just cloned a test repository. The in the cloned "w1" repository I executed:

git branch origin/master git branch remotes/origin/master git branch refs/remotes/origin/master

I now have got three *local* branches with the above names, which now seems to make it impossible to refer to the master branch from the "origin" *remote* repository.

Wouldn't it make sense to forbid such names for local branches ? For example to enforce some rules like a local branch name *must not* start with "remotes/" or "refs/" ?

so long
  Ingo
Next: Duy Nguyen
Message 1 of 2 in “Ambiguous branch names...”
  1. Ingo RohloffFeb 16, 2014
  2. Duy NguyenFeb 16, 2014

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.