From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Tue, 02 Jun 2009 04:46:33 GMT
Subject: Re: [PATCH WIP 0/4] Special code path for large blobs
Message-ID: <fcaeb9bf0906012146t7eab8dafm2b2b58aa96fb6220@mail.gmail.com>
In-Reply-To: <alpine.LFD.2.00.0905281349320.3906@xanadu.home>

2009/5/29 Nicolas Pitre <nico@cam.org>:
> 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