Re: Multiple fetches when unshallowing a shallow clone

I should point out that I never saw a "deepen 0" line. Rather, I saw git send "option depth 0" to the remote helper. Duy, you mentioned that depth=0 means "do not change depth". I assume that means the server should use exactly the shallows that the client sent, and it does not need to traverse t

Re: Multiple fetches when unshallowing a shallow clone

ags) merit a depth of zero? Doesn't depth 1 mean "give me the the objects, and none of their descendants"? Why use 0? Thanks! Jason On Fri, Dec 4, 2015 at 4:27 PM, Jeff King wrote: > On Fri, Dec 04, 2015 at 12:46:59PM -0800, Stefan Beller wrote: > >> On Mon, Nov 30,

Multiple fetches when unshallowing a shallow clone

Hi all, Would anyone be willing to help me understand some shallow-clone behavior? (I found a bug in Dulwich, and I'm looking for some context so I can determine how to fix it.) I learned that cgit sometimes performs two fetches for a `git fetch --unshallow`: one with depth 'infinity', and a sub