[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kRdBOfa85PnOTEYY-9bcEewerom_LOxucKFs_pBmcsrQ@mail.gmail.com>
Date: Tue, 20 Jan 2026 14:57:45 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Eliot Courtney <ecourtney@...dia.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nsc@...nel.org>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org
Subject: Re: [PATCH 2/6] scripts: generate_rust_analyzer: plumb editions via
command line
On Tue, Jan 20, 2026 at 9:54 AM Eliot Courtney <ecourtney@...dia.com> wrote:
>
> Add --editions argument to pass crate editions in a similar way to the
> existing --cfgs mechanism.
>
> It sets editions as follows:
> - core: 2024 for rustc >= 1.87 otherwise 2021
> - quote: 2018
> - all others: 2021
Could you please explain in the commit message the reasons behind the
change? i.e. commit messages should explain the "why" (advantages
etc.), not just the "what".
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists