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
On Mon, Feb 17, 2014 at 3:34 AM, Ingo Rohloff [off-list ref] wrote:
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/" ?
See http://thread.gmane.org/gmane.comp.version-control.git/242096/focus=242181.
The proposal basically is you can't create those branches without -f.
--
Duy