From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Joel Becker <Joel.Becker@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.33-rc7
Date: Sun, 7 Feb 2010 19:39:56 +0100 [thread overview]
Message-ID: <20100207183956.GB26388@8bytes.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1002071029040.3829@localhost.localdomain>
On Sun, Feb 07, 2010 at 10:32:02AM -0800, Linus Torvalds wrote:
> Another option might be to stop generating the .bz2 files, of course.
> Anybody who cares more about network bandwidth than CPU use (ie people who
> would seem to prefer bz2) would be better off using git instead, which
> packs things _way_ better, by virtue of being much more incremental.
The .bz2 files are downloaded by the ketchup script. I use it sometimes
to get a specific kernel tree version on a machine without having to
look up the urls to download them manually. So there are users for the
.bz2 files too ;-)
Joerg
next prev parent reply other threads:[~2010-02-07 18: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 [this message]
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=20100207183956.GB26388@8bytes.org \
--to=joro@8bytes.org \
--cc=Joel.Becker@oracle.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