On 10 December 2014 at 16:07, Junio C Hamano <gits...@pobox.com> wrote: > Jeff King <p...@peff.net> writes: >>> git reflog expire --expire=now --all && git gc --prune=now --aggressive >>> >>> Maybe: >>> >>> git gc --purge >> >> Yeah, that is common enough that it might be worthwhile (you probably >> want --expire-unreachable in the reflog invocation, though). > > Also you would not want an unconditional --aggressive.
After a big rewrite deleting files the re-optimisation of --aggressive can make a big difference to packsize - for instance 1.2GB to 768MB in a test I just ran - but of course it is *much* slower, so I suspect you're right about not including it. I wasn't aware of the '--expire-unreachable=all' switch, though it seems like a 'milder' version of the '--expire=now' switch? - in that it would keep reflog entries if they haven't been changed, which is fair enough and compatible with the 'purge' goal. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
