2009/5/29 Nicolas Pitre <nico@xxxxxxx>: > However, like I said previously, I'd encapsulate large blobs in a pack > right away instead of storing them as loose objects. The reason is that > you can effortlessly repack/fetch/push them afterwards by simply > triggering the pack data reuse code path for them. Extracting large and > undeltified blobs from a pack is just as easy as from a loose object. Makes sense. And the code looks nice too. > To accomplish that, you only need to copy write_pack_file() from > builtin-pack-objects.c and strip it to the bone with only one object to > write. write_pack_file() is too scary to me, I ripped from fast-import.c instead. BTW, how does git handle hundreds of single object packs? I don't know if prepare_packed_git scales in such cases. -- Duy -- 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