From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: "Andreas Hindborg (Samsung)" <nmi@metaspace.dk>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Alice Ryhl" <aliceryhl@google.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH] rust: upgrade to Rust 1.77.0
Date: Mon, 19 Feb 2024 17:03:41 +0100 [thread overview]
Message-ID: <CANiq72nbr6qy1otJpdh3FVUN5cUfrkUPYEHJFm_QqfKvYEj-Xw@mail.gmail.com> (raw)
In-Reply-To: <87ttm4g462.fsf@metaspace.dk>
On Mon, Feb 19, 2024 at 11:06 AM Andreas Hindborg (Samsung)
<nmi@metaspace.dk> wrote:
>
> I am a little confused about this patch, since 1.77.0 is not released
> yet and the link [1] (currently) points to the release notes for 1.76.
Yeah, the patch is written as it would have been written by the time
it is applied, i.e. see the note after `---`.
So, for instance, the link actually points to the 1.77.0 notes, it is
just that they do not exist yet :)
> Will there be a new version of this patch when 1.77 is released, or do
> we just expect no changes to alloc when the compiler goes from beta to
> release?
There can changes (or not), so it depends on that, i.e. if not, I will
apply this one. If there are non-trivial ones, then I will send a v2.
(There are no changes so far)
Cheers,
Miguel
next prev parent reply other threads:[~2024-02-19 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 0:27 [PATCH] rust: upgrade to Rust 1.77.0 Miguel Ojeda
2024-02-17 6:17 ` Boqun Feng
2024-02-19 9:05 ` Alice Ryhl
2024-02-19 16:00 ` Miguel Ojeda
2024-02-19 10:02 ` Andreas Hindborg (Samsung)
2024-02-19 16:03 ` Miguel Ojeda [this message]
2024-03-29 19:48 ` Miguel Ojeda
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=CANiq72nbr6qy1otJpdh3FVUN5cUfrkUPYEHJFm_QqfKvYEj-Xw@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nmi@metaspace.dk \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--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).