Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH website] releases: Extend 3.16 EOL to match Debian 8
Date: Thu, 21 Nov 2019 07:57:28 +0100	[thread overview]
Message-ID: <20191121065728.GA343863@kroah.com> (raw)
In-Reply-To: <20191119213141.GA19244@decadent.org.uk>

On Tue, Nov 19, 2019 at 09:31:41PM +0000, Ben Hutchings wrote:
> I'm maintaining 3.16 primarily for Debian 8.  I originally expected
> that to have an EOL of April 2020 but it's actually June.
> 
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> Acked-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
> ---
>  content/releases.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/content/releases.rst b/content/releases.rst
> index dbbe0d69db9d..0908fd090cdc 100644
> --- a/content/releases.rst
> +++ b/content/releases.rst
> @@ -45,7 +45,7 @@ Longterm
>      4.14     Greg Kroah-Hartman & Sasha Levin 2017-11-12   Jan, 2024
>      4.9      Greg Kroah-Hartman & Sasha Levin 2016-12-11   Jan, 2023
>      4.4      Greg Kroah-Hartman & Sasha Levin 2016-01-10   Feb, 2022
> -    3.16     Ben Hutchings                    2014-08-03   Apr, 2020
> +    3.16     Ben Hutchings                    2014-08-03   Jun, 2020
>      ======== ================================ ============ ==================
>  
>  Distribution kernels

Now applied to the tree, the website should update on the public side
"soon".

thanks,

greg k-h

  parent reply	other threads:[~2019-11-21  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 21:31 [PATCH website] releases: Extend 3.16 EOL to match Debian 8 Ben Hutchings
2019-11-19 21:47 ` Konstantin Ryabitsev
2019-11-21  6:57 ` Greg KH [this message]
2019-11-21 21:40   ` Ben Hutchings

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=20191121065728.GA343863@kroah.com \
    --to=greg@kroah.com \
    --cc=ben@decadent.org.uk \
    --cc=konstantin@linuxfoundation.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