On Sunday 10 February 2008 20:53, Theodore Tso wrote: > On Sun, Feb 10, 2008 at 08:07:38PM -0500, Len Brown wrote: > > A couple of hours ago I pulled my reference copy of Linux tree, > > which brought the tip here: > > > > commit 7cf712db6087342e5e7e259d3883a7b5ac3212d1 > > Merge: 58a14ee... 30ddb15... > > Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxxxxxxxx> > > Date: Sun Feb 10 12:03:57 2008 -0800 > > > > Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6 > > > > Then, 10 minutes ago I did a pull to bring the head here: > > > > commit 19af35546de68c872dcb687613e0902a602cb20e > > Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxxxxxxxx> > > Date: Sun Feb 10 14:18:14 2008 -0800 > > > > Linux 2.6.25-rc1 > > > > But this second pull seems to have re-downloaded 172MB, > > when it should have only needed the last few commits. > > Yeah, I have this problem very often when I push to the ext4 tree on > master.kernel.org. Apparently the push/pull logic isn't smart about > objects are found via objects/info/alterntaes, so it will needlessly > transfer objects that it doesn't need to. > > What I do to deal with this problem is I'll manually log into > master.kernel.org, and then use the command "git-update-ref > refs/heads/origin 19af35546de68c872dcb687613e0902a602cb20e", and then > go back and do the push/pull. Once there is a head which points to the > latest from Linus, then the push/pull logic is smart and will only > download the few commitments that aren't in the local git repository > and aren't found in a shared repository. > > Annoying, but as long as you have shell access on the machine with the > destination repository, you can work around it. yeah, I think I have see this with pushes onto kernel.org also, but unlike Ted, I simply wait. -Len - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
