From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Quentin Schulz <foss@0leil.net>,
Quentin Schulz <quentin.schulz@theobroma-systems.com>,
docs@lists.yoctoproject.org
Cc: Quentin Schulz <foss+yocto@0leil.net>
Subject: Re: [docs] [PATCH 0/4] fix some doc typos
Date: Thu, 22 Jun 2023 23:09:06 +0200 [thread overview]
Message-ID: <2fcc7aff-d4b3-10cf-a8a7-d61ed971df57@bootlin.com> (raw)
In-Reply-To: <20230622-typos-202306-v1-0-68489d7f23f2@theobroma-systems.com>
Hi Quentin,
On 22.06.23 at 18:51, Quentin Schulz wrote:
> Fix a few typos or bad formatting in the docs.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> ---
> Quentin Schulz (4):
> docs: sdk-manual: appendix-obtain: fix literal block content
> docs: ref-manual: terms: fix typos in SPDX term
> docs: fix unnecessary double white space
> docs: ref-manual: terms: fix incorrect note directive
Thanks for the fixes!
For 2, 3 and 3:
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
... and merged into master-next.
Will be happy to fix 1 if you lack time...
Thanks again
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-06-22 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 16:51 [PATCH 0/4] fix some doc typos Quentin Schulz
2023-06-22 16:51 ` [PATCH 1/4] docs: sdk-manual: appendix-obtain: fix literal block content Quentin Schulz
2023-06-22 21:02 ` [docs] " Michael Opdenacker
2023-06-22 16:51 ` [PATCH 2/4] docs: ref-manual: terms: fix typos in SPDX term Quentin Schulz
2023-06-22 16:51 ` [PATCH 3/4] docs: fix unnecessary double white space Quentin Schulz
2023-06-22 16:51 ` [PATCH 4/4] docs: ref-manual: terms: fix incorrect note directive Quentin Schulz
2023-06-22 21:09 ` Michael Opdenacker [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=2fcc7aff-d4b3-10cf-a8a7-d61ed971df57@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=foss+yocto@0leil.net \
--cc=foss@0leil.net \
--cc=quentin.schulz@theobroma-systems.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