From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"YP docs mailing list" <docs@lists.yoctoproject.org>
Cc: "BitBake developer list" <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH] doc: use monospaced font for visual clarity of options
Date: Fri, 09 Jan 2026 10:40:32 +0100 [thread overview]
Message-ID: <DFJYJRINA08I.9HHIYNCUZJSL@bootlin.com> (raw)
In-Reply-To: <569a2da6-6603-5c64-bf27-da55484a7966@crashcourse.ca>
On Thu Jan 8, 2026 at 5:25 PM CET, Robert P. J. Day wrote:
>
> Use monospaced font for command options, to make it clear when double
> dashes are being used.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> since i saw an example of this being done in the same chapter
> of the bitbake manual without quotes, i chose to do it that way.
>
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> index 329b02829..4e70eaf9d 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> @@ -538,7 +538,7 @@ The following command runs the clean task on the ``foo.bb`` recipe file::
>
> .. note::
>
> - The "-b" option explicitly does not handle recipe dependencies. Other
> + The ``-b`` option explicitly does not handle recipe dependencies. Other
> than for debugging purposes, it is instead recommended that you use
> the syntax presented in the next section.
>
> @@ -553,7 +553,7 @@ dependencies, both for build-time and runtime. There must be a way for
> you to express recipe preferences when multiple recipes provide the same
> functionality, or when there are multiple versions of a recipe.
>
> -The ``bitbake`` command, when not using "--buildfile" or "-b" only
> +The ``bitbake`` command, when not using ``--buildfile`` or ``-b`` only
> accepts a "PROVIDES". You cannot provide anything else. By default, a
> recipe file generally "PROVIDES" its "packagename" as shown in the
> following example::
> @@ -561,7 +561,7 @@ following example::
> $ bitbake foo
>
> This next example "PROVIDES" the
> -package name and also uses the "-c" option to tell BitBake to just
> +package name and also uses the ``-c`` option to tell BitBake to just
> execute the ``do_clean`` task::
>
> $ bitbake -c clean foo
Reviewed-by: Antonin Godard <antonin.godard@bootlin.com>
Thanks,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-01-09 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 16:28 [PATCH] doc: use monospaced font for visual clarity of options Robert P. J. Day
2026-01-09 9:40 ` Antonin Godard [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=DFJYJRINA08I.9HHIYNCUZJSL@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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