netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Matthias May <matthias.may@neratec.com>
Cc: Or Gerlitz <gerlitz.or@gmail.com>,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: ELOed stable kernels
Date: Thu, 19 Sep 2019 16:44:26 +0200	[thread overview]
Message-ID: <20190919144426.GA3998200@kroah.com> (raw)
In-Reply-To: <e8cf18ee-d238-8d6f-e25f-9f59b28569d2@neratec.com>

On Thu, Sep 19, 2019 at 04:39:28PM +0200, Matthias May wrote:
> On 19/09/2019 16:05, Or Gerlitz wrote:
> > Hi Greg,
> > 
> > If this is RTFM could you please point me to the Emm
> > 
> > AFAIR if a stable kernel is not listed at kernel.org than it is EOL by now.
> > 
> > Is this correct?
> > 
> > thanks,
> > 
> > Or.
> > 
> 
> You can also look at the wikipedia page at
> https://en.wikipedia.org/wiki/Linux_kernel#Maintenance_and_long-term_support
> 
> I do the updates of the entries for each release once the release-announcement has been sent to the list.
> At least since I'm doing this (last ~5 years), the last release-announcement of a branch always contains a notice that
> this release is now EOL.
> I reference all these messages for each version.

Very nice, I never noticed that!

Also, you might want to use lore.kernel.org for the email archives,
don't know who runs those other sites you link to :)

thanks,

greg k-h

  reply	other threads:[~2019-09-19 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 14:05 ELOed stable kernels Or Gerlitz
2019-09-19 14:13 ` Greg Kroah-Hartman
2019-09-19 14:39 ` Matthias May
2019-09-19 14:44   ` Greg Kroah-Hartman [this message]
2019-09-19 15:00     ` Matthias May
2019-09-19 16:34       ` Greg Kroah-Hartman

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=20190919144426.GA3998200@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=gerlitz.or@gmail.com \
    --cc=matthias.may@neratec.com \
    --cc=netdev@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).