Re: warning: no common commits - slow pull

On Friday 07 March 2008, Daniel Barkalow wrote:

On Thu, 6 Mar 2008, David Brownell wrote:

quoted

When I "git pull" it first fetches a bunch of files, then
concludes (wrongly) "no common commits", then starts a
second fetch of a *HUGE* number of files ... 400 MB is too
much to pay when updating from rc3-last-week to rc4.  But
if I interrupt that second one with ^C, it seems that the
first one fetched enough to make the next "git pull" go
pretty quickly.

Actually, if you can make a tarball of the .git directory of one of those 
workspaces, and see if the bug is reproducable with that .git directory 
every time (particularly when pulling a local repository), it would be 
really helpful to have a reliable test case.

Seems to be.  Let me know where I can stash a ~300 MB tar.bz2 file
for you ...

There's a debugging thing that would help, but it's not in your version.

So I updated.  :)

It's in next as

49aaddd102aff Teach upload-pack to log the received need lines to an fd

With that commit, you should be able to do:

GIT_DEBUG_SEND_PACK=3 git pull 3>UPLOAD_LOG

and get a file UPLOAD_LOG that will show what it's doing, although there's 
a reasonable chance that it'll only demonstrate that it's doing nothing 

That file has always been empty.

helpful, which we already pretty much know.

Oddly, a few times when I tried that the bug didn't reproduce.
One factor may be workspaces cloned a long time ago with early
versions of GIT (or cogito).

- Dave