Re: [PATCH v3 02/14] t5500: add tests of fetch-pack --all --depth=N $URL $REF
- From
Philip Oakley <philipoakley@iee.org>
- Date
- Sep 18, 2012, 23:37 UTC
- Message-ID
- <012B3B00ED9F48E5B0A8A4E21B944754@PhilipOakley>
- In-Reply-To
- <504E6141.1080306@alum.mit.edu>
From: "Michael Haggerty" <mhagger@alum.mit.edu> Sent: Monday, September 10, 2012 10:53 PM
Show 16 quoted lines
> On 09/10/2012 10:46 PM, Junio C Hamano wrote: >> Michael Haggerty <mhagger@alum.mit.edu> writes: >> >>> Document some bugs in "git fetch-pack": >>> >>> 1. If "git fetch-pack" is called with "--all", "--depth", and an >>> explicit existing non-tag reference to fetch, then it falsely >>> reports >>> that the reference was not found, even though it was fetched >>> correctly. >>> >>> 2. If "git fetch-pack" is called with "--all", "--depth", and an >>> explicit existing tag reference to fetch, then it segfaults in >>> filter_refs() because return_refs is used without having been >>> initialized. >>
This probably isn't the right place in the series but I've just see a question on SO http://stackoverflow.com/questions/12475210/git-shallow-clone-along-with-branch which gives a user case that may or may not be covered by the pack-fetch.
The user was looking for 'git clone --depth 1 -b master' and comparing it to a plain 'git clone --depth 1' and to 'git clone -b master' with the follow up question "That is, why when passing -b it seems like it's changing behaviour of --depth ?"
Perhaps something to test out.
Philip