Re: confusion over the new branch and merge config

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 21 Dec 2006 15:01:21 -0800
Junio C Hamano <junkio@xxxxxxx> wrote:

> 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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]