From: James Bruce <bruce@andrew.cmu.edu>
To: Clemens Schwaighofer <cs@tequila.co.jp>
Cc: gene.heskett@verizon.net, linux-kernel@vger.kernel.org,
"Markus T." <markus@trippelsdorf.net>
Subject: Re: Linux 2.6.9-rc3
Date: Thu, 30 Sep 2004 03:30:45 -0400 [thread overview]
Message-ID: <415BB625.9000403@andrew.cmu.edu> (raw)
In-Reply-To: <415BA7D0.7070704@tequila.co.jp>
Clemens Schwaighofer wrote:
> | And thats one of the reasons I never dl the bz2 version.
>
> what has bz2 to do with that?
Some people believe bz2 to be buggy or otherwise less tolerant of
corruption. For most people these things don't seem to come up; I've
never had problems with either despite frequent work with large
compressed datasets.
> | You should have started with a fresh unpack of 2.6.8, not 2.6.8.1
> | I just checked my scrollback and there is no such error here.
>
> well its a bit confusing. 2.6.8.1 is the latest stable right, normaly
> patches are applied against the latest stable. Let's just hope this NFS
> fix is on the rc series if you have to apply against 2.6.8
Linus decided that patches will always be off the previous
non-extraversion tarball. Note that -rc3 is not relative to -rc2, so in
that way its consistent. The reason Linus gave is that such
trivial-but-important bugfixes may come *after* the next version has
releases or release cantidates, so this is the only sane way. For
example, if another tiny code bug motivated making a 2.6.8.2, the
release cantidates shouldn't have to be rediffed. Hopefully it makes
sense now :)
- Jim Bruce
next prev parent reply other threads:[~2004-09-30 7:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 3:37 Linux 2.6.9-rc3 Linus Torvalds
2004-09-30 4:53 ` Markus T.
2004-09-30 4:59 ` Tom Duffy
2004-09-30 5:02 ` Gene Heskett
2004-09-30 6:29 ` Clemens Schwaighofer
2004-09-30 7:30 ` James Bruce [this message]
2004-09-30 7:33 ` Clemens Schwaighofer
2004-09-30 15:53 ` Ingo Saitz
2004-09-30 20:27 ` Gene Heskett
2004-09-30 21:55 ` Jeff Garzik
2004-10-01 0:42 ` Clemens Schwaighofer
2004-10-01 3:30 ` Gene Heskett
2004-10-01 3:34 ` Clemens Schwaighofer
2004-10-01 4:01 ` Gene Heskett
2004-10-01 4:05 ` Clemens Schwaighofer
2004-10-01 4:06 ` Gene Heskett
2004-10-01 3:17 ` Gene Heskett
2004-10-01 5:44 ` Christian Hesse
2004-09-30 18:58 ` Bill Davidsen
2004-09-30 20:32 ` Gene Heskett
2004-09-30 5:03 ` Tom Duffy
2004-09-30 5:14 ` Marcel Holtmann
2004-09-30 5:33 ` Tom Duffy
2004-09-30 5:20 ` Gene Heskett
2004-09-30 5:24 ` Marcel Holtmann
2004-09-30 20:41 ` Gene Heskett
2004-09-30 14:13 ` Linux 2.6.9-rc3 (compile stats) John Cherry
2004-09-30 19:03 ` Linux 2.6.9-rc3 Bill Davidsen
2004-10-01 13:49 ` [PATCH] tty fall-out (was: Re: Linux 2.6.9-rc3) Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2004-09-30 15:38 Linux 2.6.9-rc3 Tim Krieglstein
[not found] <2K07b-1Ez-3@gated-at.bofh.it>
[not found] ` <2Kh8e-5H2-23@gated-at.bofh.it>
[not found] ` <2KjMz-6E6-17@gated-at.bofh.it>
[not found] ` <2Kmr3-9n-1@gated-at.bofh.it>
2004-10-01 12:36 ` Pascal Schmidt
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=415BB625.9000403@andrew.cmu.edu \
--to=bruce@andrew.cmu.edu \
--cc=cs@tequila.co.jp \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.net \
/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