On Thu, 20 Apr 2006, Shawn Pearce wrote: > Apparently I have created a repository which v1.2.3 packs about 50% > smaller than 'next' does: > > v1.2.3 (tag): > 60M pack-7f766f5af5547554bacb28c0294bd562589dc5e7.pack > > 1.2.3.gf3a4 (an older 'next'): > 128M pack-7f766f5af5547554bacb28c0294bd562589dc5e7.pack > > 1.3.0.rc4.g8060 (a fairly recent 'next'): > 118M pack-7f766f5af5547554bacb28c0294bd562589dc5e7.pack > > Repeated packing with 1.3.0.rc4.g8060 doesn't seem to change the > size of the pack file, its pretty consistent at 118M. First try "git repack -a -d f", where the "-f" is the magic one. Without the -f, git repack will re-use old pack information, which is much much faster, but not as space-efficient. If that doesn't help, it might be time to look at the actual repo, but try that first. Linus - : 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