Re: [RFC/PATCH] define the way new representation types are encoded in the pack
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Oct 30, 2011, 09:31 UTC
- Message-ID
- <CACsJy8A1QtHS2Y-O+NmO6MNDTcG_Wqc+Q1zk0RDGei=VTuxkPg@mail.gmail.com>
- In-Reply-To
- <7v4nyrrm1w.fsf@alter.siamese.dyndns.org>
On Sun, Oct 30, 2011 at 2:11 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 7 quoted lines
>> Not sure if it's related to representation types, but is there any way >> (perhaps FLAT_BLOB type?) we can mark an object uncompressed, so we >> can mmap() and access it directly? > > In pack? Loose? Both? > > What kind of payload and use case do you have in mind?
Hmm.. big files in general with partial file transfer (e.g. git torrent). But if CAT_TREE is properly used, then all blob pieces should be reasonably small and decompress time should not be a problem. I think we won't need this. Sorry for the noise.
-- Duy