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

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

 



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
--
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]