From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: m.c.p@kernel.linux-systeme.com, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org, webmaster@kernel.org
Subject: Re: what's about 2.2 kernel?
Date: Wed, 12 Mar 2008 19:31:15 +0100 [thread overview]
Message-ID: <47D82173.3010904@gmail.com> (raw)
In-Reply-To: <20070805091131.GD6002@1wt.eu>
Willy Tarreau wrote:
> On Sun, Aug 05, 2007 at 10:41:52AM +0200, Xose Vazquez Perez wrote:
sorry, a bit old...
>> time to release a final 2.2.27 and close the
>> 2.2 tree ???
>>
>>
>> The latest 2.2 version : 2.2.26 2004-02-25 00:28 UTC
>> The latest prepatch 2.2 : 2.2.27-rc2 2005-01-12 23:55 UTC
>
> No, I think it would dupe users into thinking that 2.2.27 is up to date,
> while it would have missed a lot of security fixes. At least in the
> current situation, people tend not to trust it. It's rather sad that it
> ended that way, I've been happily putting it everywhere for a long time
> when I was telling everyone that 2.4 was an unreliable crap. I hope I
> will never set the same fate to 2.4 :-/
>
> If you're looking for updates for 2.2, you should take a look at OWL
> and PAX patches, both of those tend to include many security fixes,
> maybe they're still up to date, but I would doubt about that now.
no thanks, 2.2 looks like dead since a long time ago.
IMHO 2.2 info *must* be deleted from kernel.org _main_ page.
-thanks-
regards,
--
so much to do, so little time.
prev parent reply other threads:[~2008-03-12 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 8:41 what's about 2.2 kernel? Xose Vazquez Perez
2007-08-05 8:44 ` Jan Engelhardt
2007-08-05 9:11 ` Willy Tarreau
2008-03-12 18:31 ` Xose Vazquez Perez [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=47D82173.3010904@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@kernel.linux-systeme.com \
--cc=w@1wt.eu \
--cc=webmaster@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.