Re: confusion over the new branch and merge config

From: Junio C Hamano <junkio@cox.net>
Date: Dec 22, 2006, 00:46 UTC
Message-ID: <7vvek492q1.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20061221182102.906ad046.seanlkml@sympatico.ca>

Sean <seanlkml@sympatico.ca> writes:

> This seems inconsistent and confusing.  When working with the
> local repository, git-branch doesn't list that as "refs/heads/next"
> it just lists "next".  Why all of a sudden when trying to fetch
> it from a remote repo must a user know about "refs/heads"?

You can always say "git log refs/heads/next" even though you are allowed to say "git log next". Maybe we should remove that shorthand to make it consistent? I think not.

The remote side can add things without your knowing, so insisting on the exact match makes sense in a weird sort of way.

And this is a config file you would set once and then can forget about it. I do not see a big deal about having to spell it fully.