git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Paller-Rzepka <jasonpr@google.com>
To: git@vger.kernel.org
Subject: Multiple fetches when unshallowing a shallow clone
Date: Mon, 30 Nov 2015 14:35:04 -0500	[thread overview]
Message-ID: <CACs8u9STLLHr3c3O9kQKGEN52DLfJ2LatjWkeaeeLA-xP=gC5Q@mail.gmail.com> (raw)

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 subsequent one with
depth zero.

Could anyone answer:
1) What is the purpose of the second fetch?
2) What does this depth of zero mean? Is it the same as a depth of
infinity?  (I assume not... but, since I thought the smallest
meaningful depth was 1, I don't know what else it might mean.)

Thank you!
Jason

             reply	other threads:[~2015-11-30 19:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 19:35 Jason Paller-Rzepka [this message]
2015-12-04 20:46 ` Multiple fetches when unshallowing a shallow clone Stefan Beller
2015-12-04 21:27   ` Jeff King
2015-12-04 21:36     ` Stefan Beller
2015-12-04 21:38     ` Jason Paller-Rzepka
2015-12-04 21:50       ` Stefan Beller
2015-12-04 21:51       ` Jeff King
2015-12-04 22:45         ` Junio C Hamano
2015-12-05  5:33           ` Duy Nguyen
2015-12-06  4:00             ` Junio C Hamano
2015-12-06  6:37               ` Jeff King
2015-12-06  7:01                 ` Jeff King
2015-12-06 10:46                   ` Duy Nguyen
2015-12-07 19:57                     ` Jason Paller-Rzepka
     [not found]                     ` <CACs8u9RzUVWw2Ld1K7JeO7Eci114JEiML8bbGy96m4pZZk=FnA@mail.gmail.com>
2015-12-07 21:21                       ` Duy Nguyen
2015-12-07 21:27                   ` Junio C Hamano
2015-12-07 21:42                     ` Jeff King
2015-12-04 21:57     ` Junio C Hamano
2015-12-04 22:10       ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACs8u9STLLHr3c3O9kQKGEN52DLfJ2LatjWkeaeeLA-xP=gC5Q@mail.gmail.com' \
    --to=jasonpr@google.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).