From: Sam Vilain <sam@vilain.net>
To: Chris Wedgwood <cw@f00f.org>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org, apiszcz@lucidpixels.com
Subject: Re: Linux Kernel Source Compression
Date: Mon, 22 May 2006 09:42:28 +1200 [thread overview]
Message-ID: <4470DEC4.6050308@vilain.net> (raw)
In-Reply-To: <20060521210056.GA3500@taniwha.stupidest.org>
Chris Wedgwood wrote:
>On Sun, May 21, 2006 at 08:03:32PM +0100, Alistair John Strachan wrote:
>
>
>
>>Somebody needs to make lzma userspace tools (like p7zip) faster, not
>>crash, and behave like a regular UNIX program. Then we need a patch
>>to GNU tar to emerge, and for it to persist for at least 4
>>years. Then maybe people will adopt this format..
>>
>>
>
>why?
>
>the gains aren't that great
>
Exactly, and while I know my network connection isn't exactly
representative of the general population of people building the kernel,
it's currently faster for me to download and unpack a .gz than to wait
the extra time for bzip2 to decompress. I've always found it quicker
dealing with .gz's for incremental patches. I thought the speed issue is
more of a speed / compression ratio trade-off, ie a caveat of
compression in general.
Mind you, 'git fetch' is even faster, even for people who aren't close
enough to their mirror to fetch a full .gz kernel tarball in <5s.
Sam.
next prev parent reply other threads:[~2006-05-21 21:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 14:35 Linux Kernel Source Compression Justin Piszcz
2006-05-21 18:40 ` Jan Engelhardt
2006-05-21 18:56 ` Kasper Sandberg
2006-05-21 19:28 ` Justin Piszcz
2006-05-22 2:05 ` Stefan Smietanowski
2006-05-21 19:03 ` Alistair John Strachan
2006-05-21 21:00 ` Chris Wedgwood
2006-05-21 21:22 ` Alistair John Strachan
2006-05-21 21:42 ` Sam Vilain [this message]
2006-05-21 21:57 ` Alistair John Strachan
2006-05-21 22:22 ` Sam Vilain
2006-05-21 22:29 ` Alistair John Strachan
2006-05-22 19:00 ` H. Peter Anvin
2006-05-21 21:59 ` Diego Calleja
2006-05-22 18:58 ` H. Peter Anvin
2006-05-22 19:07 ` Alistair John Strachan
2006-05-22 19:10 ` H. Peter Anvin
2006-05-22 19:15 ` Alistair John Strachan
2006-05-22 20:24 ` Jan Engelhardt
2006-05-22 20:41 ` H. Peter Anvin
2006-05-22 21:00 ` Alistair John Strachan
2006-05-22 21:04 ` H. Peter Anvin
2006-05-22 21:11 ` Joshua Hudson
2006-05-23 13:37 ` Jan Engelhardt
2006-05-23 2:16 ` Nuri Jawad
2006-05-23 2:55 ` Stefan Smietanowski
2006-05-23 14:15 ` Ivan Novick
2006-05-23 14:23 ` Olivier Galibert
2006-05-23 14:47 ` Julian Seward
2006-05-23 16:35 ` Nuri Jawad
2006-05-25 11:42 ` Jan Engelhardt
2006-05-31 22:51 ` Bill Davidsen
2006-05-23 13:38 ` Jan Engelhardt
2006-05-23 15:28 ` Alistair John Strachan
2006-05-31 22:56 ` Bill Davidsen
2006-05-26 4:11 ` Bruce Guenter
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=4470DEC4.6050308@vilain.net \
--to=sam@vilain.net \
--cc=apiszcz@lucidpixels.com \
--cc=cw@f00f.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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