Re: PEBKAC or bug: unable to create path-like branch names

From: Daniel Barkalow <barkalow@iabervon.org>
Date: Nov 15, 2009, 07:16 UTC
Message-ID: <alpine.LNX.2.00.0911150150160.14365@iabervon.org>
In-Reply-To: <20091115050227.GD5934@penguin.codegnome.org>

On Sat, 14 Nov 2009, Todd A. Jacobs wrote:

Show 12 quoted lines

> 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.

Do you have a branch "dev/feature"? Branch names are path-like in that you can't have dev/feature as both a branch and a prefix for branches.

Show 7 quoted lines

> 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*

You want either "git check-ref-format --branch foo" or "git check-ref-format refs/heads/foo".

	-Daniel
*This .sig left intentionally blank*