On Tue, May 11, 2010 at 06:05:14AM -0400, Geert Bosch wrote: > > 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 Hmm. If that didn't solve it, then presumably it is a different problem, and I'd like to take a closer look. Is it possible for you to make a tarball of the .git directory available? > What would be the easiest way for me to repack my repository > without running reflog expire at all? Try "git repack -Ad". -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