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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Nov 30 2001 - 21:00:25 EST