All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <daiane.angolini@foundries.io>, <bitbake-devel@lists.openembedded.org>
Cc: <docs@lists.yoctoproject.org>
Subject: Re: [docs][PATCH 3/5] docs: Fix leading text for bitbake-setup init
Date: Tue, 27 Jan 2026 11:29:00 +0100	[thread overview]
Message-ID: <DFZAUOEWOS1H.14T46F1J7RX3A@bootlin.com> (raw)
In-Reply-To: <20260126222743.411405-3-daiane.angolini@foundries.io>

On Mon Jan 26, 2026 at 11:27 PM CET, Daiane Angolini via lists.yoctoproject.org wrote:
> If we use the default of bitbake-setut init we may not create anything
> (as the first default for an empty directory is N).
>
> If user does not chose a number, the script asks again for a number.
>
> Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
> ---
>  .../bitbake-user-manual-environment-setup.rst                   | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-environment-setup.rst b/doc/bitbake-user-manual/bitbake-user-manual-environment-setup.rst
> index 7bbe7cc75..e316ead56 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-environment-setup.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-environment-setup.rst
> @@ -50,7 +50,7 @@ Quick Start
>        See the :ref:`ref-bbsetup-section-config-reference` section to learn more
>        about ``bitbake-setup`` input configuration files.
>  
> -#. With the default choices, the ``bitbake-setup init`` command creates the
> +#. One example of ``bitbake-setup init`` possible command creates the
>     following files and directories::
>  
>        ./bitbake-builds/

Reviewed-by: Antonin Godard <antonin.godard@bootlin.com>

Thanks!
Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-01-27 10:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 22:27 [docs][PATCH 1/5] doc: change some terminology around bitbake-setup Daiane Angolini
2026-01-26 22:27 ` [docs][PATCH 2/5] bitbake-setup: Change the output to match the terminology in the docs Daiane Angolini
2026-01-27 10:29   ` Antonin Godard
2026-01-27 10:38     ` Alexander Kanavin
2026-01-27 13:21       ` Daiane Angolini
2026-01-27 17:45         ` Alexander Kanavin
2026-01-27 18:17           ` Daiane Angolini
2026-01-26 22:27 ` [docs][PATCH 3/5] docs: Fix leading text for bitbake-setup init Daiane Angolini
2026-01-27 10:29   ` Antonin Godard [this message]
2026-01-27 10:43     ` Alexander Kanavin
2026-01-26 22:27 ` [docs][PATCH 4/5] doc: Add the term Variant Daiane Angolini
2026-01-27 10:28   ` Antonin Godard
2026-01-27 10:46     ` Alexander Kanavin
2026-01-26 22:27 ` [docs][PATCH 5/5] docs: Fix sources as required Daiane Angolini
2026-01-27 10:28   ` [bitbake-devel] " Antonin Godard
2026-01-27 10:50     ` Alexander Kanavin
2026-01-27 13:27       ` Daiane Angolini
2026-01-27 17:46         ` Alexander Kanavin
2026-01-27 18:06           ` Daiane Angolini
2026-01-27 10:18 ` [docs][PATCH 1/5] doc: change some terminology around bitbake-setup Alexander Kanavin
2026-01-27 10:28 ` Antonin Godard
2026-01-27 10:35 ` Alexander Kanavin

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=DFZAUOEWOS1H.14T46F1J7RX3A@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=daiane.angolini@foundries.io \
    --cc=docs@lists.yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.