From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Matthew Grant <grantma@anathoth.gen.nz>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: 2.5 and beyond (was Re: New SYM53C8XX driver in 2.4.3-ac5 FIXES CD Writing!!!!)
Date: Fri, 13 Apr 2001 20:08:02 -0400 [thread overview]
Message-ID: <3AD794E2.22B55FE6@mandrakesoft.com> (raw)
In-Reply-To: <E14oDFI-0003or-00@the-village.bc.nu> <E14oDW7-0002y9-00@zion.int.anathoth.gen.nz>
Matthew Grant wrote:
> Linus,
>
> Can't we have a controlled development tree branch for 2-3 months just to get
> the ReiserFS/LVM/quota/knfsd integration done _cleanly_ (this has significant
> short-term benefits NOW), with the brakes on all other changes, and another
> development tree where everyone goes wild with NUMA/Networking et al., where
> the changes from the other get merged???
We have -got- to get 2.4 stable and sane first. It's a psychological
thing, but if Linus opens 2.5 now, people will ignore the existing 2.4
problems that need attention.
If LVM et. al. is fundamentally broken in 2.4, then mark it experimental
and support it via external patches. That's the way these things are
always dealt it, when you need a feature set beyond the existing stable
kernel.
Patience, grasshopper :)
Jeff
--
Jeff Garzik | Sam: "Mind if I drive?"
Building 1024 | Max: "Not if you don't mind me clawing at the dash
MandrakeSoft | and shrieking like a cheerleader."
prev parent reply other threads:[~2001-04-14 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E14o3J0-0002q2-00@the-village.bc.nu>
2001-04-13 23:20 ` New SYM53C8XX driver in 2.4.3-ac5 FIXES CD Writing!!!! Matthew Grant
2001-04-13 23:28 ` Alan Cox
2001-04-13 23:37 ` Matthew Grant
2001-04-13 23:44 ` Alan Cox
2001-04-14 0:02 ` Matthew Grant
2001-04-14 0:08 ` Jeff Garzik [this message]
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=3AD794E2.22B55FE6@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=grantma@anathoth.gen.nz \
--cc=linux-kernel@vger.kernel.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