Peff, thanks for your detial explain, and I think I have got the point :P
-Lingchao Xin ---------------------------------------- > Date: Wed, 14 Aug 2013 07:59:56 -0400 > From: p...@peff.net > To: dougla...@outlook.com > CC: stefanbel...@googlemail.com; git@vger.kernel.org; junchunx.g...@gmail.com > Subject: Re: About *git clone --depth=n* puzzle > > On Wed, Aug 14, 2013 at 05:19:36PM +0800, XinLingchao wrote: > >>> There was a similar discussion going on in July this year, >>> maybe this is an interesting read with respect to this topic >>> http://www.spinics.net/lists/git/msg196138.html >>> >> Stefan, I do NOT think so, the key point is not about the depth limit, >> it is about whether remote clone depth equals local clone depth. > > I do not think it is about local vs remote, but rather about which > version of git the remote side is running. Prior to 682c7d2 > (upload-pack: fix off-by-one depth calculation in shallow clone, > 2013-01-11), a shallow clone always returned one extra commit. That fix > went into v1.8.2. > > So if you have a post-v1.8.2 git client, a local clone will use the same > git version as the "remote" side of the connection. But if you are > contacting a remote server, the results you get will depend on what > version of git is running on the remote server. > > And as the example you showed uses github.com as the remote, and as I > happen to know that GitHub's servers do not currently have 682c7d2, you > would see the old behavior. > > -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
