[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72=xCYA7z7_rxpzzKkkhJs6m7L_xEaLMuArVn3ZAcyeHdA@mail.gmail.com>
Date: Wed, 30 Jul 2025 13:01:40 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Onur Özkan <work@...rozkan.dev>
Cc: rust-for-linux@...r.kernel.org, ojeda@...nel.org, alex.gaynor@...il.com,
boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
lossin@...nel.org, a.hindborg@...nel.org, aliceryhl@...gle.com,
tmgross@...ch.edu, dakr@...nel.org, me@...enk.dev, felipe_life@...e.com,
abdiel.janulgue@...il.com, dirk.behme@...bosch.com, daniel@...lak.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] rust: update `error.rs` documentation
On Wed, Jul 30, 2025 at 12:00 PM Onur Özkan <work@...rozkan.dev> wrote:
>
> I thought with that approach the documentation can become outdated
> again at some point, but I can still do it and send over v2 if you
> would prefer.
That is fine -- documentation is never perfect, but it is all about
the chance of being outdated/wrong vs. the benefits.
In this case, I think the files getting renamed and this line not
getting updated is low (and it would be still clear), and we can
eventually check if the files exist on generation.
Cheers,
Miguel
Powered by blists - more mailing lists