From: Willy Tarreau <w@1wt.eu>
To: Ferenc Wagner <wferi@niif.hu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: currently active Linux kernel versions
Date: Wed, 13 Feb 2008 11:24:36 +0100 [thread overview]
Message-ID: <20080213102436.GA3580@1wt.eu> (raw)
In-Reply-To: <87k5l9pb7d.fsf@szonett.ki.iif.hu>
On Wed, Feb 13, 2008 at 08:28:06AM +0100, Ferenc Wagner wrote:
> Willy Tarreau <w@1wt.eu> writes:
>
> > I would suggest stable - N-1 for most usages. 2.6.24.y is open, 2.6.23.y is
> > supposed to be good. The advantage when you proceed like this is that you
> > can jump from an older kernel to a more recent one which has already got its
> > share of fixes and is still maintained for some time.
> >
> > Generally, I would trust Greg when he drops an old kernel, it means that he's
> > confident enough in the next one.
>
> Thanks for the useful (and concise) summary and sharing your thoughts
> on the matter. Now my only question is: how can I learn that Greg
> updated or dropped a kernel without following LKML (which my time
> unfortunately does not permit). kernel-announce doesn't seem to
> mention such events...
Compare the release dates. If you see the latest 2.6.23.y released a week
ago and nothing equivalent for 2.6.22.y, chances are that there will not
be newer ones. Also, Greg announces his intentions to stop in each announce.
Last he stated that 2.6.22.17 (and finally 18) was most likely the last one.
Willy
next prev parent reply other threads:[~2008-02-13 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 22:37 currently active Linux kernel versions Tomasz Chmielewski
2008-02-13 0:49 ` Willy Tarreau
2008-02-13 7:28 ` Ferenc Wagner
2008-02-13 10:24 ` Willy Tarreau [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-12 20:27 Wagner Ferenc
2008-02-12 21:13 ` Xavier Bestel
2008-02-12 21:18 ` Ferenc Wagner
2008-02-12 21:21 ` Oliver Pinter
2008-02-12 21:25 ` Xavier Bestel
2008-02-12 21:37 ` Mike Snitzer
2008-02-12 21:49 ` Oliver Pinter
2008-02-13 0:29 ` Willy Tarreau
2008-02-13 7:32 ` Ferenc Wagner
2008-02-13 16:14 ` Randy Dunlap
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=20080213102436.GA3580@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=wferi@niif.hu \
/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.