Re: Remote's 'currently active branch' not HEAD?
- From
Andreas Krey <a.krey@gmx.de>
- Date
- Sep 3, 2013, 12:37 UTC
- Message-ID
- <20130903123733.GR12966@inner.h.apk.li>
- In-Reply-To
- <20130903114831.GA8559@inner.h.apk.li>
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.
At least the 'git clone' doc would be misleading then.
Andreas
-- "Totally trivial. Famous last words." From: Linus Torvalds <torvalds@*.org> Date: Fri, 22 Jan 2010 07:29:21 -0800