From: "Constantine Plotnikov" <constantine.plotnikov@gmail.com>
To: git@vger.kernel.org
Subject: [usability bug] git branch -a does not disambiguate remote and local branches
Date: Mon, 15 Dec 2008 21:15:15 +0300 [thread overview]
Message-ID: <85647ef50812151015t4d5bc2b8p4ea53a0e4ad25e64@mail.gmail.com> (raw)
Let's consider the following scenario:
mkdir bare.git
mkdir local
cd bare.git
git --bare init
cd ../local
git init
echo test > test.txt
git add test.txt
git commit -m test
git remote add origin `pwd`/../bare.git
git push --all
git checkout -b origin/master master
echo updated > test.txt
git add test.txt
git commit -m updated
Note that that in this scenario, the user has created local branch in
the folder with the same name as a remote branch. While the supposed
user here is apparently shooting itself in the foot, the scenario is
still supported by git, and might happen as a result of more logical
git operations (like git fetch).
After this scenario is executed, git branch -a will give the following output:
master
* origin/master
origin/master
Note that there is two origin/master entries, but it is not clear
which is remote is and which is the local. I think that "git branch
-a" should print unambiguous names, qualifying them if needed.
Constantine
next reply other threads:[~2008-12-15 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 18:15 Constantine Plotnikov [this message]
2008-12-15 19:09 ` [usability bug] git branch -a does not disambiguate remote and local branches Johannes Schindelin
2008-12-15 19:15 ` Constantine Plotnikov
2008-12-15 19:21 ` Boyd Stephen Smith Jr.
2008-12-15 19:24 ` Lars Hjemli
2008-12-16 6:26 ` Björn Steinbrink
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=85647ef50812151015t4d5bc2b8p4ea53a0e4ad25e64@mail.gmail.com \
--to=constantine.plotnikov@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).