Re: [PATCH 0/3] Unconfuse git clone when two branches at are HEAD.
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 6, 2013, 18:17 UTC
- Message-ID
- <xmqqfvthyfui.fsf@gitster.dls.corp.google.com>
- In-Reply-To
- <6649DD0E3B6B4CE59D330217786B6B05@PhilipOakley>
"Philip Oakley" <philipoakley@iee.org> writes:
> 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?
Not "current HEAD ref", but "git clone" will fail to check out from a bundle that does not include HEAD ref (it is easy to just say "reset --hard master" or whatever after it, though).
I think I suggested to update "git bundle" to include HEAD when there is no HEAD specified some time ago, but I do not think anybody was interested, so this may be a non-issue.