[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221013170105.kqmdxiuvi3ltnddd@gpm.stappers.nl>
Date: Thu, 13 Oct 2022 19:01:06 +0200
From: Geert Stappers <stappers@...ppers.nl>
To: Olof Johansson <olof@...om.net>, 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>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
Geert Stappers <stappers@...ppers.nl>
Subject: Re: [PATCH] scripts: rust_is_available.sh: Provide hints on how to
fix missing pieces
On Wed, Oct 05, 2022 at 09:27:44AM +0200, Geert Stappers wrote:
> On Tue, Oct 04, 2022 at 11:46:25AM -0700, Olof Johansson wrote:
> > This might be a bit bikesheddy, but it saves a few roundtrips to the
> > documentation when getting the `make LLVM=1 rustavailable` run to pass.
>
> Yeah, I have bin there :-)
>
>
> > Stick to the rustup options to avoid too much verbosity.
> >
> > Signed-off-by: Olof Johansson <olof@...om.net>
> > ---
> > scripts/rust_is_available.sh | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
>
> Reviewed-by: Geert Stappers <stappers@...ppers.nl>
How to prevent that the patch gets lost in the mail?
And how to avoid that reminders like this get contra-productive?
(When to send the next "Please approve or reject the patch"?)
Groeten
Geert Stappers
--
Silence is hard to parse
Powered by blists - more mailing lists