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. In the meantime, you can work around it with: git config gc.reflogExpireUnreachable never -Peff -- 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