Re: read-only working copies using links
- From
Sverre Rabbelier <srabbelier@gmail.com>
- Date
- Jan 24, 2009, 11:02 UTC
- Message-ID
- <bd6139dc0901240302q6b3c9a13p56fe39a976882133@mail.gmail.com>
- In-Reply-To
- <3EE64C92-CB4C-47BD-9C48-E369AED4B82F@gmail.com>
Heya,
On Sat, Jan 24, 2009 at 10:17, Chad Dombrova <chadrik@gmail.com> wrote:
Show 8 quoted lines
> the crux of the issue is that the blob objects would have to be stored as > exact copies of the original files. it would seem there are two things that > currently prevent this from happening. 1) blobs are stored with compression > and 2) they include a small header. compression can be disabled by setting > core.loosecompression to 0, so that seems like less of an issue. as for the > header, wouldn't it be possible to store it separately? in other words, > store two files per blob directory, a small stub file with the header info > and the unaltered file data.
I think Tim Ansell (cced) was talking about this at the gittogether (storing the metadata seperately), as it would benefit sparse/narrow checkout, another advantage supporting his case?
-- Cheers, Sverre Rabbelier