From: Geert Stappers <stappers@stappers.nl>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
rust-for-linux@vger.kernel.org,
Alex Gaynor <alex.gaynor@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: We are now in linux-next!
Date: Thu, 18 Mar 2021 20:26:38 +0100 [thread overview]
Message-ID: <20210318192638.o7w4zgsqycpfkbpo@gpm.stappers.nl> (raw)
In-Reply-To: <CAFRnB2XsCHJDNVL_eBF-wDpA4g1z-L9RNALt2KyQEHdfuzpQpQ@mail.gmail.com>
On Thu, Mar 18, 2021 at 08:33:05AM -0400, Alex Gaynor wrote:
> On Thu, Mar 18, 2021 at 7:00 AM Miguel Ojeda wrote:
> >
> > Hi all,
> >
> > Thanks to Stephen Rothwell, we are now in linux-next!
The commit message
in https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/rust?id=c77c8025525c36c9d2b9d82e4539403701276a1d
says there are more heroes. ;-)
> > This does not mean we will make it into mainline, of course, but it is
> > a nice step to make things as smooth as possible.
> >
> > Stephen has kindly agreed to give me a bit of leeway the first few
> > days until the RFC to rebase things as needed, which is very much
> > appreciated.
>
> Congratulations everyone, this is an exciting milestone!
Yes and as far as I understand it, has the near future
more exciting milestone on Rust for Linux.
>
> Alex
>
> --
> All that is necessary for evil to succeed is for good people to do nothing.
Groeten
Geert Stappers
--
Silence is hard to parse
prev parent reply other threads:[~2021-03-18 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 10:59 We are now in linux-next! Miguel Ojeda
2021-03-18 12:33 ` Alex Gaynor
2021-03-18 19:26 ` Geert Stappers [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=20210318192638.o7w4zgsqycpfkbpo@gpm.stappers.nl \
--to=stappers@stappers.nl \
--cc=alex.gaynor@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).