From: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reg the next LTS kernel (6.1?)
Date: Tue, 20 Dec 2022 07:15:56 +0530 [thread overview]
Message-ID: <CAPDLWs-3HiK_rNxfh=teQhGN2ZOaQE_NksKbzdRr3GcSBPJTfA@mail.gmail.com> (raw)
In-Reply-To: <20221217164059.GA4724@1wt.eu>
On Sat, Dec 17, 2022 at 10:11 PM Willy Tarreau <w@1wt.eu> wrote:
>
> On Sat, Dec 17, 2022 at 07:14:14PM +0530, Kaiwan N Billimoria wrote:
> > :-) Got it.
> > Taking your point into account, I'll rephrase: as the _convention_ is
> > to mark the last release in the year as LTS, is there any visibility
> > on when, or if, it comes about?
>
> What Greg tried to explain to you is that the convention is to pick a
> sufficiently well tested kernel to make sure its maintenance will not
> become a huge burden, and that it cannot be a single-person effort,
> testers are needed during that period. As such companies and/or users
> engaging in investing some resources for testing are extremely
> important and if some have a good reason to prefer investing that time
> on a different kernel, their choice will count more than just a kind
> request on the mailing list. Now you know how to make your voice count
> if you want/need 6.1 to become LTS.
>
Willy, Greg K-H, thanks for your guidance,
Kaiwan.
> Regards,
> Willy
next prev parent reply other threads:[~2022-12-20 1:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 7:37 Reg the next LTS kernel (6.1?) Kaiwan N Billimoria
2022-10-07 7:46 ` Greg KH
2022-10-07 7:50 ` Kaiwan N Billimoria
2022-12-17 13:02 ` Kaiwan N Billimoria
2022-12-17 13:18 ` Greg KH
2022-12-17 13:44 ` Kaiwan N Billimoria
2022-12-17 16:40 ` Willy Tarreau
2022-12-20 1:45 ` Kaiwan N Billimoria [this message]
2022-12-18 8:42 ` Greg KH
2023-01-11 8:15 ` Conor Dooley
2023-01-11 11:33 ` Greg KH
2023-01-11 19:05 ` Conor Dooley
2023-01-12 12:23 ` Kris Chaplin
2023-01-12 12:26 ` Michal Simek
2023-01-13 11:27 ` Greg KH
2023-01-13 12:54 ` Michal Simek
2023-01-13 16:22 ` Greg KH
2023-01-13 21:40 ` Theodore Ts'o
2023-01-14 7:14 ` Willy Tarreau
2023-01-14 8:26 ` Greg KH
2023-01-14 8:47 ` Willy Tarreau
2023-02-05 6:27 ` Ruslan Bilovol
2023-02-16 10:41 ` Kris Chaplin
2023-02-16 11:20 ` Greg KH
2023-02-16 11:23 ` Kris Chaplin
2023-01-16 12:16 ` Michal Simek
2023-01-17 3:07 ` Theodore Ts'o
2023-01-16 12:02 ` Michal Simek
2023-01-13 11:24 ` Greg KH
2022-10-07 15:04 Carl Dasantas
2022-10-07 15:36 ` Greg KH
2022-10-07 16:07 ` Carl Dasantas
2022-10-07 16:34 ` Greg KH
2022-10-07 19:50 ` Theodore Ts'o
2022-10-07 17:37 ` Slade Watkins
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='CAPDLWs-3HiK_rNxfh=teQhGN2ZOaQE_NksKbzdRr3GcSBPJTfA@mail.gmail.com' \
--to=kaiwan.billimoria@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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).