linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Slade Watkins <srw@sladewatkins.net>
To: Carl Dasantas <dasantas2020@gmail.com>
Cc: gregkh@linuxfoundation.org, kaiwan.billimoria@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: Reg the next LTS kernel (6.1?)
Date: Fri, 7 Oct 2022 13:37:42 -0400	[thread overview]
Message-ID: <7a034717-cc9e-c717-7578-3306fe86a5e0@sladewatkins.net> (raw)
In-Reply-To: <CANNVxH_uwnz31kak4fKAVuj8UP4wbWcFiDQ+kFwTametBvixGA@mail.gmail.com>

Hi,

This is now at least the third email I've gotten about Rust support in
the kernel. I've been ignoring them, but I'd like to say something now
and leave it at that.

On 10/7/22 at 11:04 AM, Carl Dasantas wrote:
> Please reconsidrer using 6.1 as the next LTS.
> 
> 6.0 or 5.19 is much more fitting due to not having Rust support, a
> major  change. A lot of the community is hesitant on how Rust will
> work and it would be nice to have a non-Rust capable LTS besides 5.15
> since that is already one year old. Having a more recent non-Rust
> capable LTS would make the transition more smooth as it provides a
> couple years for those of us that are hesitant to see if it goes down
> well or who knows, gets ejected altogether.

The most recent pull request for Rust support was by no means a major
change, it was _only initial support_ for Rust, nothing more than that.
Maybe I'm wrong, but after reading Kees's pull request[1], and reviewing
all the changes (which I also recommend you do, I've dropped a link
below!): it's all minor in the grand scheme of things. It's not changing
much as of me writing this.

Greg, who handles stable releases, doesn't do stable/longterm releases
based on significance, but rather, time. IOW, the yearly LTS kernel is
usually "last kernel of the year." (Greg's words, not mine.) Right now,
that appears to be 6.1 and may or may not stay that way.

I'm truly sorry you (and others, obviously) feel that way about Rust --
I'm not going to weigh in further because I don't have enough experience
with it yet -- but I really don't think it's going anywhere anytime soon.

Thanks,
-srw

[1] https://lore.kernel.org/lkml/202210010816.1317F2C@keescook/

  parent reply	other threads:[~2022-10-07 17:37 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 15:04 Reg the next LTS kernel (6.1?) 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-07  7:37 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
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

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=7a034717-cc9e-c717-7578-3306fe86a5e0@sladewatkins.net \
    --to=srw@sladewatkins.net \
    --cc=dasantas2020@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kaiwan.billimoria@gmail.com \
    --cc=linux-kernel@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).