From: "Pádraig Brady" <P@draigBrady.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.33-rc7
Date: Tue, 09 Feb 2010 11:30:34 +0000 [thread overview]
Message-ID: <4B71475A.8020209@draigBrady.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1002061445210.3829@localhost.localdomain>
On 06/02/10 22:49, Linus Torvalds wrote:
> Oh, and I forgot to ask one thing I had intended to ask in the release
> notes..
>
> Do people really care about the old-fashioned tar.gz and patch.gz files?
> I've always uploaded the tar-files and patches compressed with gzip,
> because that's the "traditional" way, and then we have a script that also
> re-compresses things as 'bz2' because it compresses better and many people
> are bandwidth-limited and much prefer the better compression.
>
> Of course, if you really care about bandwidth, you're better off just
> fetching the git trees instead, but the question for non-git users is:
>
> Would it be ok to _only_ have the 'bz2' patches and tar-balls?
>
> Having two copies of every large file seems silly, if nobody really
> requires the traditional .gz format..
For reference, we've stopped releasing bz2 files for the coreutils project.
We use gz for compatibility and xz for increased compression ratio/decompression speed.
$ rpm -q xz gzip bzip2
xz-4.999.9-0.1.beta.20091007git.fc11.i586
gzip-1.3.12-10.fc11.i586
bzip2-1.0.5-5.fc11.i586
$ bzip2 -dc linux-2.6.33-rc7.tar.bz2 | xz > linux-2.6.33-rc7.tar.xz
$ xz -dc linux-2.6.33-rc7.tar.xz | gzip > linux-2.6.33-rc7.tar.gz
$ l
-rw-rw-r-- 1 padraig 66,191,954 Feb 6 22:27 linux-2.6.33-rc7.tar.bz2
-rw-rw-r-- 1 padraig 56,347,392 Feb 9 11:17 linux-2.6.33-rc7.tar.xz
-rw-rw-r-- 1 padraig 85,300,209 Feb 9 11:20 linux-2.6.33-rc7.tar.gz
$ time bzip2 -dc linux-2.6.33-rc7.tar.bz2 >/dev/null
real 0m30.132s
$ time gzip -dc linux-2.6.33-rc7.tar.gz >/dev/null
real 0m4.996s
$ time xz -dc linux-2.6.33-rc7.tar.xz >/dev/null
real 0m11.003s
cheers,
Pádraig.
prev parent reply other threads:[~2010-02-09 11:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 22:44 Linux 2.6.33-rc7 Linus Torvalds
2010-02-06 22:49 ` Linus Torvalds
2010-02-06 23:00 ` John Kacur
2010-02-06 23:06 ` Justin P. Mattock
2010-02-07 4:54 ` Mark Lord
2010-02-07 4:58 ` Kyle McMartin
2010-02-07 5:11 ` Mark Lord
2010-02-07 5:09 ` Justin P. Mattock
2010-02-07 10:39 ` John Feuerstein
2010-02-07 19:10 ` James Cloos
2010-02-08 3:27 ` H. Peter Anvin
2010-02-07 10:20 ` Joel Becker
2010-02-07 10:43 ` Justin P. Mattock
2010-02-07 18:32 ` Linus Torvalds
2010-02-07 18:39 ` Joerg Roedel
2010-02-08 18:28 ` Pavel Machek
2010-02-08 21:49 ` Jiri Slaby
2010-02-10 8:14 ` Pavel Machek
2010-02-08 3:26 ` H. Peter Anvin
2010-02-09 11:30 ` Pádraig Brady [this message]
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=4B71475A.8020209@draigBrady.com \
--to=p@draigbrady.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.