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

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

 



On Tue, Sep 03, 2013 at 02:37:33PM +0200, Andreas Krey wrote:
> 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.
--
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]