The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Larry McVoy <lm@work.bitmover.com>,
	Tim Cambrant <tim@cambrant.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Too soon for stable release?
Date: Sat, 29 Nov 2003 17:11:11 +0000	[thread overview]
Message-ID: <20031129171111.A32154@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20031129170104.GA15333@work.bitmover.com>; from lm@bitmover.com on Sat, Nov 29, 2003 at 09:01:04AM -0800

On Sat, Nov 29, 2003 at 09:01:04AM -0800, Larry McVoy wrote:
> The news media hasn't picked up on this yet, they seem to think that
> 2.6.0 is something that will be useful.  It won't be, there will be a
> period of months during which things stablize and then you'll see the
> distros pick up the release.  I don't remember where it was exactly
> (2.4.18?) but Red Hat waited quite a while before switching to 2.4
> from 2.2.  This is normal and it works out quite well in practice.

Red Hat did a 2.4.2 release which was 2.4.2 + a lot of stability changes.
IIRC, RH7.x was based on 2.4.7, with updates to 2.4.9, 2.4.18 and finally
2.4.20-based kernels.  However, I also seem to remember each of these had
a fair number of patches applied.

I'm sure Arjan will correct me if I got the above wrong.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2003-11-29 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-29 17:49 Too soon for stable release? Tim Cambrant
2003-11-29 17:01 ` Larry McVoy
2003-11-29 17:11   ` Russell King [this message]
2003-11-29 17:42     ` Arjan van de Ven
2003-11-29 20:22       ` Stan Bubrouski
2003-11-29 17:16   ` William Lee Irwin III
2003-12-01 18:56     ` Mike Fedyk
2003-11-29 18:03   ` Tim Cambrant

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=20031129171111.A32154@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@work.bitmover.com \
    --cc=tim@cambrant.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