stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Greg KH <gregkh@linuxfoundation.org>,
	Ben Hutchings <ben.hutchings@codethink.co.uk>
Subject: Current LTS and their EOL
Date: Fri, 17 Aug 2018 08:40:06 -0700	[thread overview]
Message-ID: <20180817154006.GA3725@intel.com> (raw)

Hi Greg, Ben, and all

Is https://www.kernel.org/category/releases.html updated in terms of EOL?

Some news out of Linaro conference [2] generated a lot of doubts and questions
around.

Specially because on the way it was stated by the news 3.16 wouldn't be active
anymore. So I'm not sure about the news, but I'd like confirmation from you about
expected EOL.

[2] https://itsfoss.com/linux-lts-kernel-six-years/

Thanks in advance,
Rodrigo.

             reply	other threads:[~2018-08-17 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 15:40 Rodrigo Vivi [this message]
2018-08-17 16:17 ` Current LTS and their EOL Greg KH
2018-08-18 18:52   ` Ben Hutchings
2018-08-24 18:24     ` Greg KH
2018-08-24 19:09       ` Willy Tarreau

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=20180817154006.GA3725@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=gregkh@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).