git clone - not getting the correct default branch

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

git clone - not getting the correct default branch

Luke Diamand
A bit weird this.

I have a bare repo (managed with gitolite) which, when I clone it,
always comes up with origin/HEAD pointed to origin/master.

This despite the fact that on the repo, HEAD is a symbolic ref to origin/dev.

i.e.

% git clone git@myserver:myrepo
...
% git branch
* master

% ssh myserver
% cd /path/to/myrepo.git
% cat HEAD
ref: refs/heads/dev

What could be going wrong? Other repos don't have this problem.

Both machines are using 1.7.9.4.

Thanks,
Luke
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|

Re: git clone - not getting the correct default branch

Tomas Carnecky-2
On Wed, 18 Apr 2012 14:05:14 +0100, Luke Diamand <[hidden email]> wrote:

> A bit weird this.
>
> I have a bare repo (managed with gitolite) which, when I clone it,
> always comes up with origin/HEAD pointed to origin/master.
>
> This despite the fact that on the repo, HEAD is a symbolic ref to origin/dev.
>
> i.e.
>
> % git clone git@myserver:myrepo
> ...
> % git branch
> * master
>
> % ssh myserver
> % cd /path/to/myrepo.git
> % cat HEAD
> ref: refs/heads/dev
>
> What could be going wrong? Other repos don't have this problem.

Does master and dev in the repo on the server point to the same commit?
Because the git protocol does not expose which *branch* HEAD points to, only
which *commit*. So if two branches point to the same commit, git just takes
the first branch and points the local HEAD to that.

tom
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html