From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: "H. Peter Anvin" <hpa@zytor.com>, Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: <linux-kernel@vger.kernel.org>, <konstantin@linuxfoundation.org>
Subject: Re: 2.6.34.x longterm stable status
Date: Tue, 21 Jan 2014 10:58:48 -0500 [thread overview]
Message-ID: <52DE9938.6090804@windriver.com> (raw)
In-Reply-To: <52DE8DDD.108@zytor.com>
On 14-01-21 10:10 AM, H. Peter Anvin wrote:
> On 08/07/2013 09:07 PM, Paul Gortmaker wrote:
>>>
>>> - Shouldn't the EOL status be mentioned in the www.kernel.org front page?
>>
>> It will be marked EOL at kernel.org when it is EOL. Those that care
>> about it being EOL would have seen the message about it becoming EOL in
>> the previous 2.6.34.x release annoucement.
>>
>
> Maybe it is time to check in on this?
Yes, Konstantin just ping'd me recently on this, and the final update will
be out for review within a week; with a focus on just clear CVE like
fixes and hence a relatively smaller queue size (i.e. nothing like 200
patches etc.)
If you think it best to mark it EOL in advance of that last release,
rather than waiting for it to appear, I don't see that as a problem.
Paul.
--
>
> I just noticed that this is now over a year since the last 2.6.34
> release, which lags the last 2.6.32 release by about five months. I am
> asking because someone just queried me privately about the status of
> 2.6.34. I'm worrying if people think that security patches are still
> being backported if in fact they aren't.
>
> -hpa
>
>
next prev parent reply other threads:[~2014-01-21 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 19:32 2.6.34.x longterm stable status Aaro Koskinen
2013-08-08 4:07 ` Paul Gortmaker
2014-01-21 15:10 ` H. Peter Anvin
2014-01-21 15:58 ` Paul Gortmaker [this message]
2014-01-21 16:38 ` H. Peter Anvin
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=52DE9938.6090804@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=aaro.koskinen@iki.fi \
--cc=hpa@zytor.com \
--cc=konstantin@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox