From: Todd A. Jacobs <nospam@codegnome.org>
Date: Sun, 15 Nov 2009 05:02:27 GMT
Subject: PEBKAC or bug: unable to create path-like branch names
Message-ID: <20091115050227.GD5934@penguin.codegnome.org>
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"