Re: confusion over the new branch and merge config
- From
Sean <seanlkml@sympatico.ca>
- Date
- Dec 21, 2006, 23:21 UTC
- Message-ID
- <20061221182102.906ad046.seanlkml@sympatico.ca>
- In-Reply-To
- <7vd56cam66.fsf@assigned-by-dhcp.cox.net>
On Thu, 21 Dec 2006 15:01:21 -0800 Junio C Hamano <junkio@cox.net> wrote:
Show 5 quoted lines
> No, the message says "any REMOTE branch" -- refs/heads/next is > what it is called at the remote, and that is how the value is > expected to be spelled; I think somebody added an example to > config.txt recently to stress this. The above error messasge > obviously was not clear enough. Rewording appreciated.
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"?
This seems like an internal detail slipping into the user interface. But maybe i'm wrong, when would it ever be anything other than "refs/heads/<branch>"? If it's _always_ "refs/heads", couldn't that prefix just be assumed if not provided by the user?
Sean