From: Ingo Rohloff <lundril@gmx.de>
To: git@vger.kernel.org
Subject: Ambiguous branch names...
Date: Sun, 16 Feb 2014 21:34:39 +0100 [thread overview]
Message-ID: <20140216203439.GA15538@localhost> (raw)
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 reply other threads:[~2014-02-16 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 20:34 Ingo Rohloff [this message]
2014-02-16 22:47 ` Ambiguous branch names Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140216203439.GA15538@localhost \
--to=lundril@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.