From: Felipe Contreras <felipe.contreras@gmail.com>
To: Keith Derrick <keith.derrick@lge.com>,
Keith Derrick <keith.derrick@lge.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Cc: "simon.busch@lge.com" <simon.busch@lge.com>
Subject: RE: BUG or FEATURE? Use of '/' in branch names
Date: Fri, 02 May 2014 17:10:52 -0500 [thread overview]
Message-ID: <536417ecd0104_1c7bdcd2f0b9@nysa.notmuch> (raw)
In-Reply-To: <AAC0CF0A2CCEC34CBE983015FD81C4F7392A504B61@AICEXMBXCL02.LGE.NET>
Keith Derrick wrote:
> I can see the value in grouping branches in a directory tree under
> refs/heads, but wouldn't it make more sense to simply escape the '/'
> in the branch name so that 'hotfix/b1' is stored on disk as
> 'hotfix\/b1'?
This would be nice for remote helpers: Mercurial can have "hotfix" and
"hotifx/b1", so importing such a Mercurial repository creates problems.
--
Felipe Contreras
next prev parent reply other threads:[~2014-05-02 22:21 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 [this message]
2014-05-02 22:16 ` Junio C Hamano
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=536417ecd0104_1c7bdcd2f0b9@nysa.notmuch \
--to=felipe.contreras@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).