From: Jonathan Nieder <jrnieder@gmail.com>
To: Keith Derrick <keith.derrick@lge.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"simon.busch@lge.com" <simon.busch@lge.com>
Subject: Re: BUG or FEATURE? Use of '/' in branch names
Date: Fri, 2 May 2014 15:16:17 -0700 [thread overview]
Message-ID: <20140502221617.GO9218@google.com> (raw)
In-Reply-To: <AAC0CF0A2CCEC34CBE983015FD81C4F7392A504B61@AICEXMBXCL02.LGE.NET>
Hi Keith,
Keith Derrick wrote:
> $ git checkout -b hotfix
> Switched to a new branch 'hotfix'
> $ git checkout -b hotfix/b2
> error: unable to resolve reference refs/heads/hotfix/b2: Not a directory
> fatal: Failed to lock ref for update: Not a directory
> $
That's an ugly message. I think we can do better. (hint hint)
Longer term, I think people would like to make it possible for a
'hotfix' and 'hotfix/b2' branch to coexist, but that will take some
work, and until then, git tries to be careful about enforcing the
constraint that they cannot coexist.
Fixing it would be complicated by the need to avoid breaking people
with older versions of git when they fetch from you (what happens to
the origin/hotfix and origin/hotfix/b2 remote-tracking refs on the
client side?).
Thanks and hope that helps,
Jonathan
next prev parent reply other threads:[~2014-05-02 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5363D1B4.1000503@lge.com>
2014-05-02 22:04 ` BUG or FEATURE? Use of '/' in branch names Keith Derrick
2014-05-02 22:10 ` Felipe Contreras
2014-05-02 22:16 ` Junio C Hamano
2014-05-02 22:16 ` Jonathan Nieder [this message]
2014-05-02 22:36 ` Keith Derrick
2014-05-02 22:43 ` Jonathan Nieder
2014-05-03 7:35 ` Dennis Kaarsemaker
2014-05-04 5:39 ` Michael Haggerty
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=20140502221617.GO9218@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=keith.derrick@lge.com \
--cc=simon.busch@lge.com \
/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).