lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <h34vw3szyz4to52qzocor6qauz6gqqp47rvuqwam6m3kruwtzn@c6bralnkcjna>
Date: Mon, 1 Dec 2025 17:49:23 +0100
From: Maurice Hieronymus <mhi@...lbox.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: ojeda@...nel.org, alex.gaynor@...il.com, boqun.feng@...il.com, 
	gary@...yguo.net, bjorn3_gh@...tonmail.com, benno.lossin@...ton.me, 
	a.hindborg@...nel.org, aliceryhl@...gle.com, tmgross@...ch.edu, 
	rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] scripts: generate_rust_analyzer: Add message to
 sysroot assertion

On Mon, Dec 01, 2025 at 12:50:44AM +0100, Miguel Ojeda wrote:

> On Sun, Nov 30, 2025 at 8:15 PM Maurice Hieronymus <mhi@...lbox.org>
> wrote:
>
> > - Send patch to all people received from scripts/get_maintainer.pl
>
> Thanks for that!

I’m still getting familiar with the mailing list workflow, so I have
Ia question regarding this. You mentioned that keeping or removing the
Icomment is fine. In cases like this, if I decide not to change the
Ipatch, should I still send a reply, or would it be picked up as-is
Ieventually? 'm just curious since I plan to contribute more in the near
Ifuture.

> >      # Making sure that the `sysroot` and `sysroot_src` belong to
> >      the same toolchain.
>
> I guess we could now remove the comment since it is a bit redundant,
> but it is fine either way.

Sure, I will resend a v3 in a moment.

> Cheers, Miguel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ