From: Anuradha Ratnaweera <anuradha@gnu.org>
To: bert hubert <ahu@ds9a.nl>,
Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.4.13..
Date: Fri, 26 Oct 2001 08:17:28 +0600 [thread overview]
Message-ID: <20011026081728.A14607@bee.lk> (raw)
In-Reply-To: <Pine.LNX.4.33.0110232249090.1185-100000@penguin.transmeta.com> <20011024114026.A14078@outpost.ds9a.nl>
In-Reply-To: <20011024114026.A14078@outpost.ds9a.nl>; from ahu@ds9a.nl on Wed, Oct 24, 2001 at 11:40:26AM +0200
On Wed, Oct 24, 2001 at 11:40:26AM +0200, bert hubert wrote:
>
> On Tue, Oct 23, 2001 at 10:52:28PM -0700, Linus Torvalds wrote:
> >
> > final:
> > - page write-out throttling
> > - Pete Zaitcev: ymfpci sound driver update (make Civ:CTP happy with it)
> > - Alan Cox: i2o sync-up
> > - Andrea Arcangeli: revert broken x86 smp_call_function patch
> > - me: handle VM write load more gracefully. Merge parts of -aa VM
>
> Why do we do the exciting VM things in 'final'? We are confusing people with
> pre-patches that are better than actual releases!
IMHO _nothing_ should be done for the final. A better alternative is to name a
stable pre kernel as a final without changes. In the current scenario, a final
kernel release is one which is _not_ tested.
Cheers,
Anuradha
--
Debian GNU/Linux (kernel 2.4.13)
The most important design issue... is the fact that Linux is supposed to
be fun...
-- Linus Torvalds at the First Dutch International Symposium on Linux
next prev parent reply other threads:[~2001-10-26 2:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 5:52 linux-2.4.13 Linus Torvalds
2001-10-24 7:39 ` linux-2.4.13 christophe barbe
2001-10-24 8:08 ` linux-2.4.13 Florian Weimer
2001-10-24 8:56 ` linux-2.4.13 Tim Nicholas
2001-10-25 10:29 ` linux-2.4.13 André Dahlqvist
2001-10-24 9:40 ` linux-2.4.13 bert hubert
2001-10-24 16:51 ` linux-2.4.13 Linus Torvalds
2001-10-24 17:05 ` linux-2.4.13 high SWAP Andre Margis
2001-10-24 17:42 ` Andre Margis
2001-10-24 16:44 ` Marcelo Tosatti
2001-10-24 18:20 ` Andre Margis
2001-10-24 17:10 ` Marcelo Tosatti
2001-10-24 18:37 ` Andre Margis
2001-10-24 19:11 ` Linus Torvalds
2001-10-24 21:03 ` Lukasz Trabinski
2001-10-24 21:48 ` toon
2001-10-24 22:08 ` David S. Miller
2001-10-25 13:23 ` Christoph Rohland
2001-10-26 2:17 ` Anuradha Ratnaweera [this message]
2001-10-26 5:44 ` linux-2.4.13 Stuart Young
2001-10-24 11:16 ` linux-2.4.13 Andy Pevy
2001-10-24 10:56 ` linux-2.4.13 Francois Romieu
2001-10-24 14:48 ` linux-2.4.13 Jan Rekorajski
-- strict thread matches above, loose matches on Subject: below --
2001-10-24 14:35 linux-2.4.13 Markus Döhr
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=20011026081728.A14607@bee.lk \
--to=anuradha@gnu.org \
--cc=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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