On Wed, Apr 22, 2009 at 04:00:06PM -0400, Nicolas Pitre wrote: > And what would be the point of manually running 'git gc' then, given > that 'git gc --auto' is already invoked automatically after most commit > creating commands? > > I mean, if you consider explicit 'git gc' too long, then simply wait > until you can spare the time, if at all. This is not like a non gc'd > repository suddently becomes non functional. The other tradeoff, mentioned by Matthieu, is not about speed, but about rollover of files on disk. I think he would be in favor of a less optimal pack setup if it meant rewriting the largest packfile less frequently. However, it may be reasonable to suggest that he just not manually "gc" then. If he is not generating enough commits to warrant an auto-gc, then he is probably not losing much by having loose objects. And if he is, then auto-gc is already taking care of it. -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