From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: rust-for-linux@vger.kernel.org, Trevor Gross <tmgross@umich.edu>,
Miguel Ojeda <ojeda@kernel.org>, David Gow <davidgow@google.com>,
Alice Ryhl <aliceryhl@google.com>
Subject: Re: [PATCH v4 1/2] docs: rust: Move testing to a separate page
Date: Sun, 18 Feb 2024 21:23:55 +0100 [thread overview]
Message-ID: <CANiq72=GRUPX6wRtk6ndkxPEG8cXo_u9YB_bmg97UeHfTK=8dw@mail.gmail.com> (raw)
In-Reply-To: <20240130075117.4137360-1-dirk.behme@de.bosch.com>
On Tue, Jan 30, 2024 at 8:51 AM Dirk Behme <dirk.behme@de.bosch.com> wrote:
>
> To be able to add more testing documentation move the testing
> section to it's own page.
>
> No change on the documentation itself.
>
> Suggested-by: Trevor Gross <tmgross@umich.edu>
> Suggested-by: Miguel Ojeda <ojeda@kernel.org>
> Reviewed-by: Trevor Gross <tmgross@umich.edu>
> Reviewed-by: David Gow <davidgow@google.com>
> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
> Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
Applied to `rust-next` with fixed unordered list rendering, rewrapped
text and headers made consistent with the other documents in `rust/`
-- thanks everyone!
(I also created a "good first issue" about another bad rendering case
of an unordered list:
https://github.com/Rust-for-Linux/linux/issues/1063)
Cheers,
Miguel
prev parent reply other threads:[~2024-02-18 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 7:51 [PATCH v4 1/2] docs: rust: Move testing to a separate page Dirk Behme
2024-01-30 7:51 ` [PATCH v4 2/2] docs: rust: Add description of Rust documentation test as KUnit ones Dirk Behme
2024-02-01 2:05 ` Trevor Gross
2024-02-18 20:23 ` 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='CANiq72=GRUPX6wRtk6ndkxPEG8cXo_u9YB_bmg97UeHfTK=8dw@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=aliceryhl@google.com \
--cc=davidgow@google.com \
--cc=dirk.behme@de.bosch.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).