LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Xavier Bestel <xavier.bestel@free.fr>
To: Ferenc Wagner <wferi@niif.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: currently active Linux kernel versions
Date: Tue, 12 Feb 2008 22:25:26 +0100 [thread overview]
Message-ID: <1202851526.6697.2.camel@bip.parateam.prv> (raw)
In-Reply-To: <87wsp9q3ev.fsf@szonett.ki.iif.hu>
On mar, 2008-02-12 at 22:18 +0100, Ferenc Wagner wrote:
> Xavier Bestel <xavier.bestel@free.fr> writes:
>
> > On mar, 2008-02-12 at 21:27 +0100, Wagner Ferenc wrote:
> >
> >> which are the "currently active Linux kernel versions" at any point in
> >> time? The quote is taken from http://lkml.org/lkml/2008/2/11/29.
> >> Or more precisely: which are the "stable" versions I can depend on for
> >> a more or less critical server, those that have active security
> >> support or receive at least critical bugfixes? I know about the
> >> 2.6.2[34].y stable git trees, but I wonder how long will those receive
> >> attention (that is, security fixes). Can I find a written policy
> >> somewhere?
> >
> > The answer is at http://kernel.org/
>
> Not quite, at least I can't find 2.6.23.y there, even though that
> branch seems to be maintained...
Ah yes, sorry.
Maybe you should monitor ftp://ftp.eu.kernel.org/pub/linux/kernel/v2.6/
then.
Xav
next prev parent reply other threads:[~2008-02-12 21:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2008-02-12 22:37 Tomasz Chmielewski
2008-02-13 0:49 ` Willy Tarreau
2008-02-13 7:28 ` Ferenc Wagner
2008-02-13 10:24 ` Willy Tarreau
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=1202851526.6697.2.camel@bip.parateam.prv \
--to=xavier.bestel@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=wferi@niif.hu \
--subject='Re: currently active Linux kernel versions' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).