From: Ben Hutchings <ben@decadent.org.uk>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH website] Bump EOL date on 3.2
Date: Mon, 16 Nov 2015 19:20:43 +0000 [thread overview]
Message-ID: <20151116192043.GO17015@decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
I will continue maintaining Linux 3.2 as part of the Debian LTS
team, which is supporting Debian 7 on x86 until May 2018.
---
content/releases.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/releases.rst b/content/releases.rst
index d5dc139..cc4ea10 100644
--- a/content/releases.rst
+++ b/content/releases.rst
@@ -47,7 +47,7 @@ Longterm
3.12 Jiri Slaby 2013-11-03 2016
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 2016
+ 3.2 Ben Hutchings 2012-01-04 May, 2018
2.6.32 Willy Tarreau 2009-12-03 Early 2016
======== ==================== ============ ==================
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
reply other threads:[~2015-11-16 19:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20151116192043.GO17015@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=konstantin@linuxfoundation.org \
--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).