From: Philip Oakley <philipoakley@iee.org>
Date: Fri, 06 Sep 2013 17:29:16 GMT
Subject: Re: [PATCH 0/3] Unconfuse git clone when two branches at are HEAD.
Message-ID: <6649DD0E3B6B4CE59D330217786B6B05@PhilipOakley>
In-Reply-To: <20130906155204.GE12966@inner.h.apk.li>

From: "Andreas Krey" <a.krey@gmx.de>
> Ok, here are some patches that make git actually
> check out the current remote branch when cloning.
>
> Up to now this failed when there were two branches that pointed to
> the HEAD commit of the remote repo, and git clone would sometimes
> choose the wrong one as the HEAD ref isn't transmitted in all
> transport.
>
> Stuff the HEAD ref into the capability list (assuming refs are clean
> enough to do that w/o escaping), and read them out on the other
> side. All other things were thankfully already in place.
>
> Two of the patches have Junio in the From as they are essentially his.
>
> Andreas
> --

Does this have any impact on the alleged bug in `git bundle --all` 
(which can then be cloned from) where the current HEAD ref wasn't 
included in the bundle? Or am I mis-remembering?

Philip