From: Chris Mason <mason@suse.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "C. Scott Ananian" <cscott@cscott.net>,
Nicolas Pitre <nico@cam.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 18:43:52 -0400 [thread overview]
Message-ID: <200505041843.53469.mason@suse.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505041501220.2328@ppc970.osdl.org>
On Wednesday 04 May 2005 18:03, Linus Torvalds wrote:
> On Wed, 4 May 2005, Chris Mason wrote:
> > Yes, if Linus does take the patches, it's really important for people to
> > be able to easily continue without deltas/packing if they want.
>
> I'll happily take the patch and just not use the delta packing myself (at
> least until I trust it). But before I take the patch I want to make sure
> that people agree on it, and that it's been tested well enough that it
> won't cause people to corrupt their repositories.
>
> For example, I do _not_ want to be in the situation SVN is in, where if
> you corrupt your SVN database, you're totally screwed. There's a real
> advantage to not having fancy data structures or complicated consistency
> rules.
Fair enough ;) I'm pretty flexible about most of the details, so I'm hoping
it won't be hard to get a consensus. The current code might be a little too
simple in format (in the packed and delta headers), but so far it seems
sufficient for git's needs.
The git-pack utility would probably be the best way to get other people to
experiment and make suggestions, so I'll start there.
-chris
next prev parent reply other threads:[~2005-05-04 22:38 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
2005-05-04 17:44 ` Chris Mason
2005-05-04 22:03 ` Linus Torvalds
2005-05-04 22:43 ` Chris Mason [this message]
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=200505041843.53469.mason@suse.com \
--to=mason@suse.com \
--cc=alonz@nolaviz.org \
--cc=cscott@cscott.net \
--cc=git@vger.kernel.org \
--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).