From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH v2] overview-manual: inform the reader early of "bitbake-getvar"
Date: Tue, 26 May 2026 09:52:54 +0200 [thread overview]
Message-ID: <DISG1ZV3PGFC.1FK9GGQXRM8RM@bootlin.com> (raw)
In-Reply-To: <f4adc33f-5b48-bd89-e872-fa387921aa2d@crashcourse.ca>
On Fri May 22, 2026 at 6:35 PM CEST, Robert P. J. Day wrote:
>
> Given how Chapter 4 of the Overview Manual introduces so many of the
> variables that define a build, briefly introduce the reader to the
> "bitbake-getvar" command so they can examine those variables.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/documentation/overview-manual/concepts.rst b/documentation/overview-manual/concepts.rst
> index 0dac5cfbc..5c6df883a 100644
> --- a/documentation/overview-manual/concepts.rst
> +++ b/documentation/overview-manual/concepts.rst
> @@ -14,9 +14,9 @@ explained.
> .. note::
>
> Throughout this section, many variables and their meanings are
> - introduced. If, in the context of a build directory, you want to
> - examine the value of any of these variables, you can use the
> - ``bitbake-getvar`` command, explained in the
> + introduced. If, in the context of a :term:`Build Directory`,
> + you want to examine the value of any of these variables, you can
> + use the ``bitbake-getvar`` command, explained in the
> ":ref:`dev-manual/debugging:viewing variable values`" section.
>
> Yocto Project Components
You sent this but it is based on your v1. I squashed this one and v1 locally,
just wanted to let you know.
Antonin
next prev parent reply other threads:[~2026-05-26 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 16:38 [PATCH v2] overview-manual: inform the reader early of "bitbake-getvar" Robert P. J. Day
2026-05-26 7:52 ` Antonin Godard [this message]
2026-06-09 7:27 ` 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=DISG1ZV3PGFC.1FK9GGQXRM8RM@bootlin.com \
--to=antonin.godard@bootlin.com \
--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