From: Linus Torvalds <torvalds@osdl.org>
To: Keith Packard <keithp@keithp.com>
Cc: Nicolas Pitre <nico@cam.org>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Repacking many disconnected blobs
Date: Wed, 14 Jun 2006 14:17:27 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606141415540.5498@g5.osdl.org> (raw)
In-Reply-To: <1150319115.30681.54.camel@neko.keithp.com>
On Wed, 14 Jun 2006, Keith Packard wrote:
>
> > In that case it
> > might be preferable that the reuse of already deltified data is made of
> > backward delta which is the reason you might consider feeding object in
> > the prefered order up front.
>
> Hmm. As I'm deltafying along branches, the delta data should actually be
> fairly good; the only 'bad' result will be the sub-optimal object
> ordering in the pack files. I'll experiment with some larger trees to
> see how much additional savings the various repack options yield.
The fact that git repacking sorts by filesize after it sorts by filename
should make this a non-issue: we always try to delta against the larger
version (where "larger" is not only almost invariable also "newer", but
the delta is simpler, since deleting data doesn't take up any space in the
delta, while adding data needs to ay what the data added was, of course).
Linus
next prev parent reply other threads:[~2006-06-14 21:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 7:17 Repacking many disconnected blobs Keith Packard
2006-06-14 7:29 ` Shawn Pearce
2006-06-14 9:07 ` Johannes Schindelin
2006-06-14 12:33 ` Junio C Hamano
2006-06-14 9:37 ` Sergey Vlasov
2006-06-14 15:53 ` Linus Torvalds
2006-06-14 17:55 ` Keith Packard
2006-06-14 18:18 ` Linus Torvalds
2006-06-14 18:52 ` Linus Torvalds
2006-06-14 18:59 ` Keith Packard
2006-06-14 19:18 ` Linus Torvalds
2006-06-14 19:25 ` Nicolas Pitre
2006-06-14 21:05 ` Keith Packard
2006-06-14 21:17 ` Linus Torvalds [this message]
2006-06-14 21:20 ` Nicolas Pitre
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=Pine.LNX.4.64.0606141415540.5498@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=keithp@keithp.com \
--cc=nico@cam.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.
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).