On Wed, May 24, 2006 at 11:41:26AM -0700, Junio C Hamano wrote: > > $ git-name-rev 0bcf7932d0ea742e765a40b > > 0bcf7932d0ea742e765a40b master > > $ git-name-rev 54e938a80873e85f9c02ab4 > > 54e938a80873e85f9c02ab4 34k-2.6.16.18 > > $ git-name-rev 2d0a9369c540519bab8018e > > 2d0a9369c540519bab8018e 34k-2.6.16.18~1 > > $ git-name-rev bf3060065ef9f0a8274fc32 > > bf3060065ef9f0a8274fc32 34k-2.6.16.18~2 > > $ git-name-rev 27602bd8de8456ac619b77c > > 27602bd8de8456ac619b77c 34k-2.6.16.18~3 > > > > It's sending every object back to the start of history ... > > Is this "master" commit 0bcf79 part of v2.6.16.18 history? If > not, how diverged are you? That is, what does this command tell > you? No, the master branch is where the MIPS development happens and it's tracking Linus' master branch. The fact that I'm talking about this in context of -stable / v2.6.16.18 is that I started looking into why things were taking minutes when doing a small fetch from 2.6.16-stable. It happens just as well with Linus' tree or yet others like Matthias Urlich's -mm git tree. > git rev-list b7d0617..master | wc -l > > Here, b7d0617 is the name of the commit object that is pointed > by v2.6.16.18 tag. $ git rev-list b7d0617..master | wc -l 12845 $ git rev-list master..b7d0617 | wc -l (that is swapped arguments) 173 $ Ralf - : 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