{"thread":{"id":"35893","subject":"Ambiguous branch names...","startedAt":"2014-02-16T20:34:39Z","lastAt":"2014-02-16T22:47:16Z","messageCount":2,"participants":["Ingo Rohloff","Duy Nguyen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"234907","messageId":"20140216203439.GA15538@localhost","threadId":"35893","inReplyTo":null,"subject":"Ambiguous branch names...","fromName":"Ingo Rohloff","fromEmail":"lundril@gmx.de","sentAt":"2014-02-16T20:34:39Z","receivedAt":"2014-02-16T20:34:39Z","isPatch":false,"sender":{"key":"lundril@gmx.de","avatar":null},"body":"Hello,\n\nwhile trying out git (version 1.7.9.5), I did this:\n\ngit clone -- ssh://myserver/~rohloff/git/w1.git w1\n\nSo I just cloned a test repository.\nThe in the cloned \"w1\" repository I executed:\n\ngit branch origin/master\ngit branch remotes/origin/master\ngit branch refs/remotes/origin/master\n\nI now have got three *local* branches with the above names, which\nnow seems to make it impossible to refer to the master branch\nfrom the \"origin\" *remote* repository.\n\nWouldn't it make sense to forbid such names for local branches ?\nFor example to enforce some rules like a local branch name *must not*\nstart with \"remotes/\" or \"refs/\" ?\n\nso long\n  Ingo\n"},{"id":"234908","messageId":"CACsJy8Cfv0-QQBX=Psm28wWbpM8Jra4POPUGgsFbn6EB2Yk9Zw@mail.gmail.com","threadId":"35893","inReplyTo":"20140216203439.GA15538@localhost","subject":"Re: Ambiguous branch names...","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2014-02-16T22:47:16Z","receivedAt":"2014-02-16T22:47:16Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Mon, Feb 17, 2014 at 3:34 AM, Ingo Rohloff <lundril@gmx.de> wrote:\n> Hello,\n>\n> while trying out git (version 1.7.9.5), I did this:\n>\n> git clone -- ssh://myserver/~rohloff/git/w1.git w1\n>\n> So I just cloned a test repository.\n> The in the cloned \"w1\" repository I executed:\n>\n> git branch origin/master\n> git branch remotes/origin/master\n> git branch refs/remotes/origin/master\n>\n> I now have got three *local* branches with the above names, which\n> now seems to make it impossible to refer to the master branch\n> from the \"origin\" *remote* repository.\n>\n> Wouldn't it make sense to forbid such names for local branches ?\n> For example to enforce some rules like a local branch name *must not*\n> start with \"remotes/\" or \"refs/\" ?\n\nSee http://thread.gmane.org/gmane.comp.version-control.git/242096/focus=242181.\nThe proposal basically is you can't create those branches without -f.\n-- \nDuy\n"}]}