From: Greg KH <gregkh@linuxfoundation.org>
To: Wedson Almeida Filho <wedsonaf@gmail.com>
Cc: rust-for-linux@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] Retiring from the Rust for Linux project
Date: Thu, 29 Aug 2024 08:35:29 +0200 [thread overview]
Message-ID: <2024082923-unthawed-fracture-6e1b@gregkh> (raw)
In-Reply-To: <20240828211117.9422-1-wedsonaf@gmail.com>
On Wed, Aug 28, 2024 at 06:11:16PM -0300, Wedson Almeida Filho wrote:
> Hey folks,
>
> This is as short a series as one can be: just removing myself as maintainer of
> the Rust for Linux project.
>
> I am retiring from the project. After almost 4 years, I find myself lacking the
> energy and enthusiasm I once had to respond to some of the nontechnical
> nonsense, so it's best to leave it up to those who still have it in them.
>
> To the Rust for Linux team: thank you, you are great. It was a pleasure working
> with you all; the times we spent discussing technical issues, finding ways to
> address soundness holes, etc. were something I always enjoyed and looked
> forward to. I count myself lucky to have collaborated with such a talended and
> friendly group.
>
> I wish all the success to the project.
>
> I truly believe the future of kernels is with memory-safe languages. I am no
> visionary but if Linux doesn't internalize this, I'm afraid some other kernel
> will do to it what it did to Unix.
Sad to see you go, we wouldn't have been able come this far without you.
But good news, now you have more time to actually write more code, we
all know maintainers don't get much time to do that! :)
Again, thanks for all of the work and effort you have done here, it is
greatly appreciated.
> Lastly, I'll leave a small, 3min 30s, sample for context here:
> https://youtu.be/WiPp9YEBV0Q?t=1529 -- and to reiterate, no one is trying force
> anyone else to learn Rust nor prevent refactorings of C code.
No one sane ever thought that.
thanks again for all of your effort, I suggest adding an entry to the
CREDITS file for the work that you have done as is traditional for when
maintainers step down.
thanks,
greg k-h
prev parent reply other threads:[~2024-08-29 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 21:11 [PATCH 0/1] Retiring from the Rust for Linux project Wedson Almeida Filho
2024-08-28 21:11 ` [PATCH 1/1] MAINTAINERS: Remove Wedson as Rust maintainer Wedson Almeida Filho
2024-09-02 9:43 ` Miguel Ojeda
2024-08-28 22:20 ` [PATCH 0/1] Retiring from the Rust for Linux project Miguel Ojeda
2024-08-29 2:39 ` Alex Gaynor
2024-08-29 6:35 ` Greg KH [this message]
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=2024082923-unthawed-fracture-6e1b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/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).