All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bradley Chapman <kakadu_croc@yahoo.com>
To: Jeff Garzik <jeff@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Clean up older Kernels
Date: Mon, 1 Dec 2003 12:32:46 -0800 (PST)	[thread overview]
Message-ID: <20031201203246.99655.qmail@web40907.mail.yahoo.com> (raw)

Mr. Garzik,

> > On Mon, Dec 01, 2003 at 08:40:47PM +0100, Thomas Babut wrote:
> > Hi,
> >
> > perhaps my question is unusual, but why do you not clean up the older Linux
> > Kernels?
> >
> > The Kernel 2.0.39 is the last stable one, but there is also a 2.0.40-rc6. So
> > why not releasing it as stable 2.0.40 (final)? And Alan Cox isn't active any
> > more for some time and the ac-Patches are very old. They could be removed,
> > or not?
>
> 2.0.x has a maintainer, David Winehall(sp?) IIRC. Poke him... :)
>
> I agree, might as well put out 2.0.40...

I've been wondering about this too, but I was afraid to ask first :-)

When 2.6 is officially released as a stable kernel and 2.4 is relegated to security/
bugfix-only status, what will happen to 2.0 and 2.2? Obviously, they won't be
totally ignored for support reasons (not everyone uses 2.4 - see counter.li.org),
but what will Mr. Anvin do to the frontpage of kernel.org?

Brad

=====


__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

             reply	other threads:[~2003-12-01 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01 20:32 Bradley Chapman [this message]
2003-12-01 20:50 ` Clean up older Kernels Jeff Garzik
2003-12-01 21:20   ` Bradley Chapman
  -- strict thread matches above, loose matches on Subject: below --
2003-12-01 19:40 Thomas Babut
2003-12-01 19:49 ` Jeff Garzik

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=20031201203246.99655.qmail@web40907.mail.yahoo.com \
    --to=kakadu_croc@yahoo.com \
    --cc=jeff@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.