From: Jeff Garzik <jgarzik@pobox.com>
To: Thomas Babut <thomas.babut@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Clean up older Kernels
Date: Mon, 1 Dec 2003 14:49:05 -0500 [thread overview]
Message-ID: <20031201194905.GB7273@gtf.org> (raw)
In-Reply-To: <000001c3b843$04f94330$5f00a8c0@tomek.lan>
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...
Jeff
next prev parent reply other threads:[~2003-12-01 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 19:40 Clean up older Kernels Thomas Babut
2003-12-01 19:49 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-01 20:32 Bradley Chapman
2003-12-01 20:50 ` Jeff Garzik
2003-12-01 21:20 ` Bradley Chapman
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=20031201194905.GB7273@gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.babut@gmx.de \
/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