From: Keith Derrick <keith.derrick@lge•com>
To: Jonathan Nieder <jrnieder@gmail•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 18:36:59 -0400 [thread overview]
Message-ID: <53641E0B.5000706@lge.com> (raw)
In-Reply-To: <20140502221617.GO9218@google.com>
Yes, I've since found some discussion on this, and had already changed
to use '-' to append the classifier.
But the other problem is that I can't easily find this restriction
documented anywhere - which means it comes as a suprise to people.
As it stands, the documentation implies that what I tried should work.
In which case, how it's been *implemented* seems to be breaking the
promise of the functional specification (if you view the documentation
as such).
Keith
On 05/02/2014 03:16 PM, Jonathan Nieder wrote:
> 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:39 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
2014-05-02 22:36 ` Keith Derrick [this message]
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=53641E0B.5000706@lge.com \
--to=keith.derrick@lge$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jrnieder@gmail$(echo .)com \
--cc=simon.busch@lge$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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