From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: quentin.schulz@theobroma-systems.com
Cc: Quentin Schulz <foss+yocto@0leil.net>, docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH v2] docs: sdk-manual: appendix-obtain: fix literal block content
Date: Mon, 17 Jul 2023 17:58:56 +0200 [thread overview]
Message-ID: <8ce2d2f1-870b-96fc-23df-e754dc664aa1@bootlin.com> (raw)
In-Reply-To: <0db2c074-f292-60bd-8bbe-17a27c65055f@theobroma-systems.com>
On 26.06.23 at 08:43, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Michael,
>
> On 6/23/23 19:54, michael.opdenacker@bootlin.com wrote:
>> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>>
>> From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
>>
>> Restore the error message as it is supposed to be issued.
>>
>> The literal block renders its content verbatim so a term role (`:term:`)
>> would appear as :term: string in there and `---` as --- string instead
>> of the expected hyphen.
>>
>> Fixes: e319b3bf4eb6 ("manuals: add missing references to SDKMACHINE
>> and SDK_ARCH")
>> Cc: Quentin Schulz <foss+yocto@0leil.net>
>> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
>> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
>>
>
> It'll teach me to send a patch in a hurry before taking a day off :)
>
> Thanks, lgtm.
Thanks Quentin. That's better than not sending the patch anyway!
Merged into master-next.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-07-17 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <176B16FDD157E15A.20970@lists.yoctoproject.org>
2023-06-23 17:54 ` [PATCH v2] docs: sdk-manual: appendix-obtain: fix literal block content michael.opdenacker
2023-06-26 6:43 ` Quentin Schulz
2023-07-17 15:58 ` 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=8ce2d2f1-870b-96fc-23df-e754dc664aa1@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=foss+yocto@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