On Wed, Aug 03, 2011 at 04:56:43PM +0000, Udo wrote:
> I have a remote bare repository with two branches 'master' and 'testing', where
> HEAD refers to 'testing'. When cloning this repository git checks out 'master',
> if 'master' and 'testing' are on the same revision (i.e. HEAD == testing ==
> master). Only if 'testing' is one (or more) commit(s) behind or ahead, git clone
> checks out the 'testing' branch on the local side. I tried this with git 1.7.5
> on Mac OS X (10.6.8).
Yes, this is a known issue.
The git protocol just sends the list of refs and the objects they point
to. So the local clone is forced to guess which ref HEAD is pointing to.
E.g., with something like:
28f599b... HEAD
1234abc... refs/heads/master
28f599b... refs/heads/testing
it can see that HEAD is probably "testing". But if it sees:
28f599b... HEAD
28f599b... refs/heads/master
28f599b... refs/heads/testing
then it has to pick one arbitrarily. Our current heuristic is to prefer
"master" over others, and otherwise pick first alphabetically. So it's
at least deterministic, but as you noticed, it's not always right.
The real solution to this would be to extend the git protocol to convey
symbolic ref information (and then wait for both client and server to be
upgraded). Some patches have been floated in the past, but nothing came
of it[1]. Maybe it's time to resurrect them.
As a workaround, you can use "git clone -b testing ..." if you know
ahead of time that "testing" is what you want.
-Peff
[1] See:
http://thread.gmane.org/gmane.comp.version-control.git/102039
and also:
http://article.gmane.org/gmane.comp.version-control.git/113567
--
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