From: Guenter Roeck <linux@roeck-us.net>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
webmaster@kernel.org, LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux kernels with LongTerm Support (LTS) VS. End-Of-Life [EOL]
Date: Tue, 9 Sep 2014 22:24:48 -0700 [thread overview]
Message-ID: <20140910052448.GA26888@roeck-us.net> (raw)
In-Reply-To: <CA+icZUWKsPzZ0rC_11zNnE9-D4MLO7TjvakKyT5P1u=uqbqZDA@mail.gmail.com>
On Tue, Sep 09, 2014 at 02:52:47PM +0200, Sedat Dilek wrote:
> Oh cool.
> Hmm, is it possible to link all "longterm:" labeled kernels to the
> page you pointed me to?
>
You mean following the "Releases" link on the top of the page
is too difficult to find ?
Guenter
> - Sedat -
>
> On Tue, Sep 9, 2014 at 2:27 PM, Konstantin Ryabitsev
> <konstantin@linuxfoundation.org> wrote:
> > On Tue, Sep 09, 2014 at 02:25:24PM +0200, Sedat Dilek wrote:
> >> Hi,
> >>
> >> it's a cool idea to label Linux-kernels with an "EOL" on the mainpage
> >> of <kernel.org>.
> >> But how can someone see how long a LongTerm Support (LTS) L-k is supported?
> >> Is it possible to add a date line or a web-link on the mainpage?
> >
> > https://www.kernel.org/releases.html
> >
> > --
> > Konstantin Ryabitsev
> > Linux Foundation Collab Projects
> > Montréal, Québec
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2014-09-10 5:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 12:25 Linux kernels with LongTerm Support (LTS) VS. End-Of-Life [EOL] Sedat Dilek
2014-09-09 12:27 ` Konstantin Ryabitsev
2014-09-09 12:52 ` Sedat Dilek
2014-09-10 5:24 ` Guenter Roeck [this message]
2014-09-10 8:02 ` Sedat Dilek
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=20140910052448.GA26888@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=webmaster@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