From: Junio C Hamano <gitster@pobox.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, 02 May 2014 15:16:07 -0700 [thread overview]
Message-ID: <xmqq61lnakt4.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <AAC0CF0A2CCEC34CBE983015FD81C4F7392A504B61@AICEXMBXCL02.LGE.NET> (Keith Derrick's message of "Fri, 2 May 2014 18:04:29 -0400")
Keith Derrick <keith.derrick@lge.com> writes:
> The problem arises when a branch already exists with a name
> matching the stem of the new branch name.
> ...
> But, for the reverse reason, I can't now create the branch named 'hotfix'
All correct. Allowing '/' in branch names came about not with a
careful design but was done by a happy accident, and we accepted it
under the condition "as long as users know that they cannot have
branches D and D/F at the same time, that is fine".
An obvious alternative convention you can adopt would be to use not
'/' but some other separating characters (e.g. "_") as your
hierarchy delimiter, if you must have D and D_F at the same time.
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 [this message]
2014-05-02 22:16 ` Jonathan Nieder
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=xmqq61lnakt4.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.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 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.