From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Patrick Miller <paddymills@proton.me>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] docs: rust: make section names plural
Date: Mon, 26 May 2025 20:44:54 +0200 [thread overview]
Message-ID: <CANiq72nwwQdzgiC4QLX6BkJ_bDUS-qTCfe0UKrPCiAF5k_P=SQ@mail.gmail.com> (raw)
In-Reply-To: <20241002022749.390836-1-paddymills@proton.me>
On Wed, Oct 2, 2024 at 4:28 AM Patrick Miller <paddymills@proton.me> wrote:
>
> Fixes existing rust documentation section headers to be use plural names.
>
> Signed-off-by: Patrick Miller <paddymills@proton.me>
> Suggested-by: Miguel Ojeda <ojeda@kernel.org>
> Link: https://github.com/Rust-for-Linux/linux/issues/1110
Applied to `rust-next` -- thanks!
[ Removed the `init` one that doesn't apply anymore and
reworded slightly. - Miguel ]
For context: https://lore.kernel.org/rust-for-linux/CANiq72nhNmLMdFTzpSQSxxMLanFA7Od6tBZ+3CrVERv9Spou5Q@mail.gmail.com/
Cheers,
Miguel
prev parent reply other threads:[~2025-05-26 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 2:28 [PATCH v5 1/2] docs: rust: make section names plural Patrick Miller
2024-10-02 2:29 ` [PATCH v5 2/2] checkpatch: warn on known non-plural rust doc headers and empty doc comments Patrick Miller
2024-10-02 11:56 ` Miguel Ojeda
2024-10-02 12:28 ` Joe Perches
2024-10-02 12:31 ` Hridesh Mg
2024-10-02 12:46 ` Miguel Ojeda
2025-05-26 18:44 ` Miguel Ojeda [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANiq72nwwQdzgiC4QLX6BkJ_bDUS-qTCfe0UKrPCiAF5k_P=SQ@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=paddymills@proton.me \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=wedsonaf@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).