From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <foss@0leil.net>,
<bitbake-devel@lists.openembedded.org>
Cc: <docs@lists.yoctoproject.org>,
"Quentin Schulz" <quentin.schulz@cherry.de>
Subject: Re: [docs] [PATCH 1/3] doc: fix a few typos
Date: Thu, 04 Dec 2025 14:16:56 +0100 [thread overview]
Message-ID: <DEPGLUHKFVDU.65FX6MWV8NWY@bootlin.com> (raw)
In-Reply-To: <20251203-doc-file-include-require-v1-1-fc708832b475@cherry.de>
On Wed Dec 3, 2025 at 6:06 PM CET, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
>
> Some spurious whitespaces, bad grammar and typo are fixed here.
>
> Fixes: 7bd36f6c6d33 ("doc: extend classes and include/require documentation")
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
> doc/bitbake-user-manual/bitbake-user-manual-intro.rst | 4 ++--
> doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> index 9837b009e..2875e18f3 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> @@ -213,7 +213,7 @@ BitBake supports class files installed in three different directories:
>
> - ``classes-global/``: these classes must be inherited globally through the
> :term:`INHERIT` variable in a :ref:`configuration file
> - <bitbake-user-manual/bitbake-user-manual-intro:Configuration Files>`. These
> + <bitbake-user-manual/bitbake-user-manual-intro:Configuration Files>`. These
> classes are included for every recipe being built. For example, you would use
> the global class named ``myclass`` like so::
>
> @@ -227,7 +227,7 @@ BitBake supports class files installed in three different directories:
> inherit myclass
>
> - ``classes/``: this final directory is meant for classes that can be used in
> - the two contexts explain above. In other words, they can be inherit either
> + the two contexts explain above. In other words, they can be inherited either
> globally or in a recipe.
>
> For details on how BitBake locates class files, see the
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
> index e5075a346..ef8ab024d 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
> @@ -1060,7 +1060,7 @@ Additionally, BitBake searches the current directory for :ref:`include
>
> .. note::
>
> - The BBPATH variable is analogous to the environment variable PATH .
> + The BBPATH variable is analogous to the environment variable PATH.
>
> For these two directives, BitBake includes the first file it finds.
>
> @@ -1135,7 +1135,7 @@ would be searched in this order::
>
> .. note::
>
> - Note that the order of the list above does not depend on where the class in
> + Note that the order of the list above does not depend on where the class is
> inherited from.
>
> Likewise, for classes inherited with the :term:`INHERIT` variable, the
Reviewed-by: Antonin Godard <antonin.godard@bootlin.com>
Thank you!
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-12-04 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 17:06 [PATCH 0/3] doc: bitbake-user-manual: few fixes related to locating include files Quentin Schulz
2025-12-03 17:06 ` [PATCH 1/3] doc: fix a few typos Quentin Schulz
2025-12-04 13:16 ` Antonin Godard [this message]
2025-12-03 17:06 ` [PATCH 2/3] doc: bitbake-user-manual-intro: specify inherit_defer directive for recipe classes Quentin Schulz
2025-12-04 13:16 ` [docs] " Antonin Godard
2025-12-03 17:06 ` [PATCH 3/3] doc: bitbake-user-manual-metadata: reorder introduction on how to locate include files Quentin Schulz
2025-12-04 13:16 ` [docs] " Antonin Godard
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=DEPGLUHKFVDU.65FX6MWV8NWY@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=foss@0leil.net \
--cc=quentin.schulz@cherry.de \
/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