On Mon, Sep 01, 2008 at 08:00:37PM -0400, Jeff King wrote: > It looks like the gc.autopacklimit defaults to 50, which would have > helped this. Pasky, is repo.or.cz not gc-ing? Or gc-ing with different > parameters? Or is this an artifact of the forking infrastructure (i.e., > these packs are actually split across multiple modules)? Unfortunately, I'm not aware how to decreate the packs count with current Git without losing _any_ objects. So yes, you could say that this is an artifact of the forking infrastructure - we just can't afford to lose objects. I've been meaning to look into this for few... years now, but there is always too many more important things to do. If anyone wants to help out, you're welcome to! :-) Maybe I should just give up on the whole alternates idea. Unless the referenced object store is practically static, it just does not seem as a feasible thing to do with Git at all, and disk space is cheap. -- Petr "Pasky" Baudis The next generation of interesting software will be done on the Macintosh, not the IBM PC. -- Bill Gates -- 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
