Re: Remote's 'currently active branch' not HEAD?

From: Michael Schubert <mschub@elegosoft.com>
Date: Sep 3, 2013, 13:02 UTC
Message-ID: <20130903130250.GB20459@pc.elego.de>
In-Reply-To: <20130903123733.GR12966@inner.h.apk.li>

On Tue, Sep 03, 2013 at 02:37:33PM +0200, Andreas Krey wrote:

Show 9 quoted lines

> On Tue, 03 Sep 2013 13:48:31 +0000, Andreas Krey wrote:
> ...
> > I now have a sample repo that reproduces this behaviour.
> > Unpack tar file, clone, see clone having 'wrong' branch
> > checked out, apparently independent of the transport:
> 
> Ouch, it looks like 'git clone' doesn't actually know
> the 'current remote branch' but picks one of those that
> happen to have the HEAD *commit* as their tip.

Yes, it picks the first of those:

http://thread.gmane.org/gmane.comp.version-control.git/168144

> At least the 'git clone' doc would be misleading then.