From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Swami <swami310@gmail.com>
Cc: michael.opdenacker@rootcommit.com,
bitbake-devel@lists.openembedded.org,
docs@lists.yoctoproject.org
Subject: Re: [PATCH v5] bitbake-user-manual: Documenting BB_CMDLINE
Date: Thu, 4 Dec 2025 10:54:50 +0000 (UTC) [thread overview]
Message-ID: <af10c84c-1bda-42f4-ace0-74e7d3306cfb@rootcommit.com> (raw)
In-Reply-To: <20251204002531.7660-1-swami310@gmail.com>
Hi Swani
Thanks for the update!
On 12/4/25 01:25, Swami wrote:
> Add documentation for the internal read-only variable :term:`BB_CMDLINE`.
> Fixes [YOCTO #15746]
> Signed-off-by: Swaminathan K <swami310@gmail.com>
> ---
> doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> index 734c7858a..00b28519a 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> @@ -116,6 +116,10 @@ overview of their function and contents.
> Specifies if SSL certificates should be checked when fetching. The default
> value is ``1`` and certificates are not checked if the value is set to ``0``.
>
> + :term:`BB_CMDLINE`
> + :term:`BB_CMDLINE` is an internal variable and is read-only. It captures the exact
> + command line used for the current invocation of BitBake.
> +
Oops, you have unnecessary spaces in your last line. Please remove them.
My editor flags those and this is distracting for a reviewer.
Unless Antonin prefers to fix this by himself.
If you send a V6, you can also move "the exact" to the next line.
Otherwise, your line is longer than 80
characters and it also stands out a little bit.
Sorry, documentation patches are the most difficult ones 😅
Thanks for your patience!
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
next parent reply other threads:[~2025-12-04 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251204002531.7660-1-swami310@gmail.com>
2025-12-04 10:54 ` Michael Opdenacker [this message]
[not found] ` <CA+-_CqnmcJ1txe-AuECK-sJ+N-+itruvAtQAkpNPQh4ckhPFFw@mail.gmail.com>
2025-12-04 12:57 ` [bitbake-devel] [PATCH v5] bitbake-user-manual: Documenting BB_CMDLINE 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=af10c84c-1bda-42f4-ace0-74e7d3306cfb@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=swami310@gmail.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