From: David Lang <dlang@digitalinsight.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Compression and dictionaries
Date: Mon, 14 Aug 2006 10:34:12 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0608141033080.14796@qynat.qvtvafvgr.pbz> (raw)
In-Reply-To: <44E0AFCB.10908@garzik.org>
On Mon, 14 Aug 2006, Jeff Garzik wrote:
> Date: Mon, 14 Aug 2006 13:15:55 -0400
> From: Jeff Garzik <jeff@garzik.org>
> To: Jakub Narebski <jnareb@gmail.com>
> Cc: git@vger.kernel.org
> Subject: Re: Compression and dictionaries
>
> Jakub Narebski wrote:
>> David Lang wrote:
>>
>>> the other factor that was mentioned was that a single-bit corruption in
>>> the dictionary would make the entire pack file useless. if this is really
>>> a concern then just store multiple copies of the dictionary. on a pack
>>> with lots of files in it it can still be a significant win.
>>
>> Or use some error-correcting code for storing dictionary.
>
> Error-correcting code? We have sha1 hash to determine validity...
that would only tell you that what you have is garbage (and you need to restore
from backup(, useing a ECC costs some space, but lets you recover from some
errors without having to resort to backups.
David Lang
next prev parent reply other threads:[~2006-08-14 17:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 3:37 Compression and dictionaries Jon Smirl
2006-08-14 3:56 ` Shawn Pearce
2006-08-14 4:07 ` Jon Smirl
2006-08-14 4:17 ` Shawn Pearce
2006-08-14 7:48 ` Alex Riesen
2006-08-14 10:06 ` Erik Mouw
2006-08-14 12:33 ` Johannes Schindelin
2006-08-14 14:08 ` Jon Smirl
2006-08-14 14:45 ` Johannes Schindelin
2006-08-14 16:15 ` Jon Smirl
2006-08-14 16:32 ` David Lang
2006-08-14 16:55 ` Jakub Narebski
2006-08-14 17:15 ` Jeff Garzik
2006-08-14 17:34 ` David Lang [this message]
2006-08-14 17:50 ` Jeff Garzik
2006-08-14 18:48 ` Jon Smirl
2006-08-14 19:08 ` David Lang
2006-08-14 19:38 ` Johannes Schindelin
2006-08-14 15:14 ` Alex Riesen
2006-08-14 15:26 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2006-08-15 8:33 linux
2006-08-15 13:29 ` Jon Smirl
2006-08-15 14:55 ` Jon Smirl
2006-08-16 0:37 ` linux
[not found] ` <4b73d43f0608152243i15b37036x7aa50aa3afc2b02f@mail.gmail.com>
2006-08-16 5:50 ` Jon Smirl
2006-08-16 6:33 ` Johannes Schindelin
2006-08-16 6:55 ` Shawn Pearce
2006-08-16 7:09 ` Johannes Schindelin
2006-08-16 14:43 ` Jon Smirl
2006-08-17 22:33 ` linux
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.63.0608141033080.14796@qynat.qvtvafvgr.pbz \
--to=dlang@digitalinsight.com \
--cc=git@vger.kernel.org \
--cc=jeff@garzik.org \
--cc=jnareb@gmail.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.
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).