From: Mike Fedyk <mfedyk@matchmail.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: David Relson <relson@osagesoftware.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Releases
Date: Mon, 26 Nov 2001 20:21:29 -0800 [thread overview]
Message-ID: <20011126202129.A26219@mikef-linux.matchmail.com> (raw)
In-Reply-To: <4.3.2.7.2.20011124231412.00b40c50@mail.osagesoftware.com> <Pine.LNX.3.96.1011126151758.27112G-100000@gatekeeper.tmr.com>
In-Reply-To: <Pine.LNX.3.96.1011126151758.27112G-100000@gatekeeper.tmr.com>
On Mon, Nov 26, 2001 at 03:42:29PM -0500, Bill Davidsen wrote:
> NOTE: this might mean that 2.4.18-pre1 would be out before
> 2.4.17 was actually released. That may bother some people.
[snip]
> least until it is in a development series and has been tested. If it were
> up to me I would have opened 2.5 when 2.4.0 was released, and all the VM
> stuff would have happened there. That's just the way I would assure
The new VM was integrated too late, and 2.4 released too early.
I agree with Linus... You do need a _known_ starting point for the next dev
kernel. 2.4.15 is known.
Also, having a 17-rc and 18-pre (at the same time) would load down Marcello
much more, and I haven't seen anyone else try it.
If 2.4 stayed 2.3 a bit longer, maybe it would've been cought maybe not.
Who knows if Andrea would've written his new VM back then.
What is interesting now is how Rik's VM (patch against 2.4.16) looks now
that it is seperate from the hugeness of the -ac patch.
The point is, if 2.4.0 was more mature, Linus *could* have given it over to
a maintainer sooner and started 2.5. Instead, we ended up with a quasi
dev/stable kernel, and no dev "idiot if you don't expect corruption" kernel.
During that time there was no *rock* in 2.4 (unless it crashed - which
hasn't happened to me). More like packed dirt. ;)
MF
next prev parent reply other threads:[~2001-11-27 4:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 4:27 Kernel Releases David Relson
2001-11-25 5:49 ` John Alvord
2001-11-25 6:34 ` CaT
2001-11-25 14:12 ` John Jasen
2001-11-26 7:15 ` John Alvord
2001-11-25 15:46 ` Eric W. Biederman
2001-11-25 16:23 ` Nathan Walp
2001-11-26 21:03 ` Bill Davidsen
2001-11-25 19:55 ` Phil Sorber
2001-11-26 9:22 ` Allan Sandfeld
2001-11-26 14:51 ` Ian Stirling
2001-11-26 15:02 ` Rik van Riel
2001-11-26 19:11 ` Ian Stirling
2001-11-26 19:55 ` vda
2001-11-26 20:42 ` Bill Davidsen
2001-11-27 4:21 ` Mike Fedyk [this message]
2001-11-27 9:50 ` Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2001-11-25 5:37 Dan Kegel
2001-11-25 9:25 ` Nathan Dabney
2001-11-25 10:24 ` Keith Owens
2001-11-25 13:34 ` Phil Howard
2001-11-25 19:03 ` Nathan Dabney
2001-11-26 10:46 Martin Knoblauch
2001-11-26 15:27 ` John Jasen
2001-11-26 20:36 ` Horst von Brand
2001-11-27 2:40 ` Gerhard Mack
2001-11-27 17:25 Dan Kegel
2001-11-27 17:36 ` François Cami
2001-11-27 17:38 ` Dan Kegel
2001-11-27 18:13 ` Vitaly Luban
2001-11-28 16:23 ` Horst von Brand
2001-11-28 19:17 ` Mike Fedyk
[not found] <fa.dac7a7v.1hkofg8@ifi.uio.no>
2001-11-27 17:53 ` Giacomo Catenazzi
[not found] <Pine.LNX.4.33.0111261807570.489-100000@mikeg.weiden.de>
2001-11-27 18:08 ` vda
2001-11-27 16:58 ` Mike Galbraith
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=20011126202129.A26219@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=relson@osagesoftware.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