From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Slaby <jirislaby@gmail.com>
Subject: Re: [PATCH kernel.org] change 3.12 EOL
Date: Mon, 11 Apr 2016 11:50:32 -0400 [thread overview]
Message-ID: <20160411155032.GA8904@gmail.com> (raw)
In-Reply-To: <1460278097-4595-1-git-send-email-jslaby@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
On Sun, Apr 10, 2016 at 10:48:17AM +0200, Jiri Slaby wrote:
> From: Jiri Slaby <jirislaby@gmail.com>
>
> Since SLE12-SP1 is based upon 3.12 and its EOL is in 2017, move the
> EOL of 3.12 to 2017 too.
>
> Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
> ---
> content/releases.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/content/releases.rst b/content/releases.rst
> index 28ebf47834..14494a64cd 100644
> --- a/content/releases.rst
> +++ b/content/releases.rst
> @@ -44,7 +44,7 @@ Longterm
> 4.1 Sasha Levin 2015-06-21 Sep, 2017
> 3.18 Sasha Levin 2014-12-07 Jan, 2017
> 3.14 Greg Kroah-Hartman 2014-03-30 Aug, 2016
> - 3.12 Jiri Slaby 2013-11-03 2016
> + 3.12 Jiri Slaby 2013-11-03 Jan, 2017
> 3.10 Greg Kroah-Hartman 2013-06-30 End of 2015
> 3.4 Li Zefan 2012-05-20 Sep, 2016
> 3.2 Ben Hutchings 2012-01-04 May, 2018
Merged and deployed.
Best,
--
Konstantin Ryabitsev
Linux Foundation Collab Projects
Montréal, Québec
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-11 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 8:48 [PATCH kernel.org] change 3.12 EOL Jiri Slaby
2016-04-11 15:50 ` Konstantin Ryabitsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-11 17:26 Xose Vazquez Perez
2016-04-11 17:45 ` Greg KH
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=20160411155032.GA8904@gmail.com \
--to=konstantin@linuxfoundation.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--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).