From: Mark Lord <kernel@teksavvy.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: Sat, 06 Feb 2010 23:54:43 -0500 [thread overview]
Message-ID: <4B6E4793.3010201@teksavvy.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1002061445210.3829@localhost.localdomain>
Linus Torvalds wrote:
> 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.
..
I prefer the .gz files, despite limited bandwidth here.
My older, slower CPUs cope with them better.
But .bz2-only would be fine as well.
I just wish the GNU tar folk had the sense to combine -z and -j
into a single flag.
-ml
next prev parent reply other threads:[~2010-02-07 4:54 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 [this message]
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
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=4B6E4793.3010201@teksavvy.com \
--to=kernel@teksavvy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox