From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [website PATCH v2] 4.1 is a longterm kernel.
Date: Wed, 23 Sep 2015 16:12:01 -0700 [thread overview]
Message-ID: <20150923231201.GA4515@kroah.com> (raw)
In-Reply-To: <20150923214840.GA29324@kroah.com>
I'll be maintaining 4.1 for the next two years, proving that after a
decade of doing stable kernels, I still do not know any better.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
v2 - 4.1 was released in 2015, not 2014, thanks to kees for pointing
that out.
diff --git a/content/releases.rst b/content/releases.rst
index b0dd13311c92..be33e9289cb1 100644
--- a/content/releases.rst
+++ b/content/releases.rst
@@ -40,6 +40,7 @@ Longterm
======== ==================== ============ ==================
Version Maintainer Released Projected EOL
======== ==================== ============ ==================
+ 4.1 Greg Kroah-Hartman 2015-08-30 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
diff --git a/pelicanconf.py b/pelicanconf.py
index f0ca020f531b..0bebac28bab3 100644
--- a/pelicanconf.py
+++ b/pelicanconf.py
@@ -24,7 +24,7 @@ import sys
sys.path.append('./')
from plugins import releases
-LONGTERM_KERNELS = ('3.18', '3.14', '3.12', '3.10', '3.4', '3.2', '2.6.34', '2.6.32')
+LONGTERM_KERNELS = ('4.1', '3.18', '3.14', '3.12', '3.10', '3.4', '3.2', '2.6.34', '2.6.32')
EOL_KERNELS = ('2.6.34', '3.0', '3.7', '3.8', '3.9', '3.11', '3.13', '3.15', '3.16', '3.17', '3.19', '4.0')
GIT_MAINLINE = '/mnt/git-repos/repos/pub/scm/linux/kernel/git/torvalds/linux.git'
next prev parent reply other threads:[~2015-09-23 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 21:48 [website PATCH] 4.1 is a longterm kernel Greg Kroah-Hartman
2015-09-23 23:12 ` Greg Kroah-Hartman [this message]
2015-09-23 23:14 ` [website PATCH v3] " Greg Kroah-Hartman
2015-09-24 0:19 ` 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=20150923231201.GA4515@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mricon@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