On May 11, 2010, at 01:01, Jeff King wrote: > On Mon, May 10, 2010 at 01:58:11PM -0400, Geert Bosch wrote: > >> On my recent MacBook Pro, I gave up after reflog expire --all >> had chewed up 30 minutes of perfectly fine CPU time. > > There are some corner cases that can cause the expire-unreachable > algorithm to behave badly. The fix is b4ca1db (reflog > --expire-unreachable: avoid merge-base computation, 2010-04-07), but > hasn't been included in a release yet. > I tried with v1.7.1 + cherry-pick b4ca1db968eb57d9cd869337bffa254e0b2c83bd, but that didn't solve the issue. > In the meantime, you can work around it with: > > git config gc.reflogExpireUnreachable never I had tried that too, but I guess I'll just have to be very patient: 22707 ttys001 11:14.27 git reflog expire --all What would be the easiest way for me to repack my repository without running reflog expire at all? -Geert -- 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