From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Greg KH <gregkh@linuxfoundation.org>, stable <stable@vger.kernel.org>
Subject: Re: Stable release 3.12.74
Date: Thu, 11 May 2017 18:11:51 -0400 [thread overview]
Message-ID: <20170511221151.GD2253@gmail.com> (raw)
In-Reply-To: <db252a03-11a1-6c42-f57e-726167bc563b@suse.cz>
On Wed, May 10, 2017 at 08:22:39AM +0200, Jiri Slaby wrote:
>On 05/09/2017, 04:15 PM, Greg KH wrote:
>> On Tue, May 09, 2017 at 03:19:30PM +0200, Jiri Slaby wrote:
>>> Greg, could you release 3.12.74 for me, please?
>>>
>>> This is very likely the LAST 3.12 release.
>>
>> Nice! Thanks for doing this for so long. Do you want us to mark it EOL
>> on kernel.org?
>
>Yes, Konstantin, please mark 3.12 as EOL.
Marked 3.12 as EOL and reflected as such on the site. Sorry for the
delay!
-K
next prev parent reply other threads:[~2017-05-11 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 13:19 Stable release 3.12.74 Jiri Slaby
2017-05-09 14:15 ` Greg KH
2017-05-10 6:22 ` Jiri Slaby
2017-05-11 22:11 ` Konstantin Ryabitsev [this message]
2017-05-12 13:05 ` [PATCH kernel.org] 3.12 is really gone Greg KH
2017-05-12 14:41 ` Konstantin Ryabitsev
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=20170511221151.GD2253@gmail.com \
--to=konstantin@linuxfoundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).