Junio C Hamano <gitster@xxxxxxxxx> writes: > Jeff King <peff@xxxxxxxx> writes: > >> On Thu, Oct 04, 2012 at 04:14:54PM +0200, Markus Trippelsdorf wrote: >> >>> with current trunk I get the following on an up-to-date Linux tree: >>> >>> markus@x4 linux % time git pull >>> Already up-to-date. >>> git pull 7.84s user 0.26s system 92% cpu 8.743 total >>> >>> git version 1.7.12 is much quicker: >>> >>> markus@x4 linux % time git pull >>> Already up-to-date. >>> git pull 0.10s user 0.02s system 16% cpu 0.740 total >> >> Yikes. I can easily reproduce here. Bisecting between master and >> v1.7.12 gives a curious result: the slowdown first occurs with the merge >> commit 34f5130 (Merge branch 'jc/merge-bases', 2012-09-11). But neither >> of its parents is slow. I don't see anything obviously suspect in the >> merge, though. > > I think the following is likely to be the correct solution to this. No, it is not. Sorry for the noise. -- 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