From: Sverre Rabbelier <srabbelier@gmail.com>
To: Chad Dombrova <chadrik@gmail.com>,
"Tim 'Mithro' Ansell" <tansell@google.com>
Cc: git@vger.kernel.org
Subject: Re: read-only working copies using links
Date: Sat, 24 Jan 2009 12:02:36 +0100 [thread overview]
Message-ID: <bd6139dc0901240302q6b3c9a13p56fe39a976882133@mail.gmail.com> (raw)
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:
> 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
next prev parent reply other threads:[~2009-01-24 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 9:17 read-only working copies using links Chad Dombrova
2009-01-24 11:02 ` Sverre Rabbelier [this message]
2009-01-24 18:39 ` Chad Dombrova
2009-01-24 18:43 ` Sverre Rabbelier
2009-01-24 19:35 ` Jeff King
2009-01-24 19:34 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd6139dc0901240302q6b3c9a13p56fe39a976882133@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=chadrik@gmail.com \
--cc=git@vger.kernel.org \
--cc=tansell@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).