> I do not think that would help the original poster's situation > where only 5 revs result in a 1.5G pack. I would _almost_ say > "do not pack such a repository", but there is the initial > cloning over git-aware transports which always results in a > repository with a single pack. Huh? Why not? That repository has a lot of files. For compression, you want all versions of a file in one pack, and with few versions that makes it easier to split up, not harder. As for network transport of packs, I haven't studied the details, but if you allow "thin packs" that have deltas relative to objects not in the pack, then breaking up the pack anywhere should be legal. Or, if necessary, you can stuff an arbitrarily large file through git-unpack-objects, which reads a stream from stdin without attempting to mmap it. (Speaking of unpack-objects.c, what's that "static unsigned long eof" variable in there? It never seems to be set to a non-zero value.) - : 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