[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mT_N0eSkUAR9KYYWvFaVNYYOpFiJLr_whab=FNFcMVhw@mail.gmail.com>
Date: Fri, 15 Dec 2023 12:35:58 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Tiago Lam <tiagolam@...il.com>
Cc: Viresh Kumar <viresh.kumar@...aro.org>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>, Wedson Almeida Filho <wedsonaf@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>, Jonathan Corbet <corbet@....net>,
Vincent Guittot <vincent.guittot@...aro.org>, rust-for-linux@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] docs: rust: Clarify that 'rustup override' applies to
build directory
On Fri, Dec 15, 2023 at 12:14 PM Tiago Lam <tiagolam@...il.com> wrote:
>
> I think we can drop the reference to the `--path <buildir>` to avoid
> giving too much information to the users following the guide. It doesn't
> seem to bring anything given users should now always go through `make
> rustupoverride`.
Yeah, the idea with the new target was to simplify this, rather than
have it as an additional way.
> But if I understood this correctly, the point here is that with the new
> target we can now abstract both cases behind the `make rustupoverride`
> target - i.e. we don't need to provide alternatives.
Exactly.
Cheers,
Miguel
Powered by blists - more mailing lists