From: "Todd A. Jacobs" <nospam@codegnome.org>
To: git@vger.kernel.org
Subject: PEBKAC or bug: unable to create path-like branch names
Date: Sat, 14 Nov 2009 21:02:27 -0800 [thread overview]
Message-ID: <20091115050227.GD5934@penguin.codegnome.org> (raw)
In-Reply-To: <20091115020605.GE15966@cl.cam.ac.uk>
I want to create a nested feature branch, but git keeps complaining if I
nest more than one level deep:
$ git checkout -b dev/feature/foo
error: unable to resolve reference refs/heads/dev/feature/foo:
Not a directory
fatal: Failed to lock ref for update: Not a directory
Based on my reading of the manual pages, it seems like I should be able
to nest branch names as long as it conforms to certain rules. I read
git-branch(1), which points me to git-check-ref-format(1), which seems
to say that the rules are being followed.
On the other hand, running:
$ git check-ref-format foo; echo $?
always results in a non-zero error code, even with a literal 'foo' as a
branch name, so clearly it isn't saying what I think it's saying.
*shrug*
Can someone provide a little clarity here?
--
"Oh, look: rocks!"
-- Doctor Who, "Destiny of the Daleks"
next prev parent reply other threads:[~2009-11-15 5:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 2:06 Preserving empty directories when doing a git-svn clone/rebase Steven J. Murdoch
2009-11-15 5:02 ` Todd A. Jacobs [this message]
2009-11-15 5:36 ` PEBKAC or bug: unable to create path-like branch names Jacob Helwig
2009-11-15 7:36 ` Todd A. Jacobs
2009-11-15 7:55 ` Jacob Helwig
2009-11-15 7:16 ` Daniel Barkalow
2009-11-16 3:32 ` Preserving empty directories when doing a git-svn clone/rebase Eric Wong
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=20091115050227.GD5934@penguin.codegnome.org \
--to=nospam@codegnome.org \
--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).