From: "C. Scott Ananian" <cscott@cscott.net>
To: Chris Mason <mason@suse.com>
Cc: Nicolas Pitre <nico@cam.org>, Linus Torvalds <torvalds@osdl.org>,
Alon Ziv <alonz@nolaviz.org>,
git@vger.kernel.org
Subject: Re: [PATCH] add the ability to create and retrieve delta objects
Date: Wed, 4 May 2005 12:12:38 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0505041202270.22203@cag.csail.mit.edu> (raw)
In-Reply-To: <200505041156.19499.mason@suse.com>
On Wed, 4 May 2005, Chris Mason wrote:
> 3) create a git-pack tool that can pack/unpack existing changesets,trees and
> files, optionally adding/removing deltas.
A 'git-pull' tool might be more use. I can imagine Linus maintaining his
local tree uncompressed, but the 'kernel.org' tree set up to
git-pull-delta from him every hour or whatever, so that the
network-accessible version is always network-efficient. 'git-pack'
would then simplify to a git-pull-delta from an existing local repository.
Ideally, you'd also be able to git-pull from a network packed repository
and (transparently) unpack and undelta-fy the pulled files as they're
added to your local repo. This would keep Linus from accidentally getting
packed files in his tree when he pulled from a maintainer's
packed/delta-ed network-accessible tree.
I'd also be interested in seeing the speed/space numbers for some other
delta chain lengths between 1 and 16. Maybe some intermediate point is
optimal. [Also, limiting delta chains to a certain number of other
*packed* objects -- instead of just 'objects' -- might be an improvement.
Right now you're packing entire commits together, right? Maybe defining a
delta chain as 'N other commits max' might improve i/o performance, as
you'd just have to keep N other unpacked files around, instead of an
arbitrary number.]
--scott
SSBN 743 BOND ESGAIN SUMAC ZPSECANT MHCHAOS Castro Flintlock payment
anthrax SCRANTON PLO MKNAOMI DNC AVBLIMP RUFUS Secretary AK-47 Noriega
( http://cscott.net/ )
next prev parent reply other threads:[~2005-05-04 16:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 3:57 RFC: adding xdelta compression to git Alon Ziv
2005-05-03 4:12 ` Nicolas Pitre
2005-05-03 4:52 ` Linus Torvalds
2005-05-03 5:30 ` Davide Libenzi
2005-05-03 15:52 ` C. Scott Ananian
2005-05-03 17:35 ` Linus Torvalds
2005-05-03 18:10 ` Davide Libenzi
2005-05-03 8:06 ` [PATCH] add the ability to create and retrieve delta objects Nicolas Pitre
2005-05-03 11:24 ` Chris Mason
2005-05-03 12:51 ` Nicolas Pitre
2005-05-03 15:07 ` Linus Torvalds
2005-05-03 16:09 ` Chris Mason
2005-05-03 15:57 ` C. Scott Ananian
2005-05-03 16:35 ` Chris Mason
2005-05-03 14:13 ` Chris Mason
2005-05-03 14:24 ` Nicolas Pitre
2005-05-03 14:37 ` Chris Mason
2005-05-03 15:04 ` Nicolas Pitre
2005-05-03 16:54 ` Chris Mason
2005-05-03 14:48 ` Linus Torvalds
2005-05-03 15:52 ` Nicolas Pitre
2005-05-04 15:56 ` Chris Mason
2005-05-04 16:12 ` C. Scott Ananian [this message]
2005-05-04 17:44 ` Chris Mason
2005-05-04 22:03 ` Linus Torvalds
2005-05-04 22:43 ` Chris Mason
2005-05-05 3:25 ` Nicolas Pitre
2005-05-04 21:47 ` Geert Bosch
2005-05-04 22:34 ` Chris Mason
2005-05-05 3:10 ` Nicolas Pitre
2005-05-03 12:48 ` RFC: adding xdelta compression to git Dan Holmsand
2005-05-03 15:50 ` C. Scott Ananian
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0505041202270.22203@cag.csail.mit.edu \
--to=cscott@cscott.net \
--cc=alonz@nolaviz.org \
--cc=git@vger.kernel.org \
--cc=mason@suse.com \
--cc=nico@cam.org \
--cc=torvalds@osdl.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).