Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN via buildroot" <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] docs/manual: fix typo in merged-bin details
Date: Thu, 13 Nov 2025 17:41:42 +0100	[thread overview]
Message-ID: <aRYKRrNl6nALDwmo@landeda> (raw)
In-Reply-To: <20251112203227.27573-1-peter@korsgaard.com>

Peter, All,

On 2025-11-12 21:32 +0100, Peter Korsgaard spake thusly:
> Commit 6b53649bfa ("docs/manual: add merged-bin details to customize
> rootfs") added a small typo, fix that.
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Reviewed-by: Yann E. MORIN <yann.morin.1998@free.fr>

Thanks!

Regards,
Yann E. MORIN.

> ---
>  docs/manual/customize-rootfs.adoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/docs/manual/customize-rootfs.adoc b/docs/manual/customize-rootfs.adoc
> index 5d8bcba778..4d03d04617 100644
> --- a/docs/manual/customize-rootfs.adoc
> +++ b/docs/manual/customize-rootfs.adoc
> @@ -31,7 +31,7 @@ When +BR2_ROOTFS_MERGED_USR+ is enabled, then the overlay must not
>  Additionally, when +BR2_ROOTFS_MERGED_BIN+ is enabled, then the overlay
>    must not contain the '/usr/sbin' directory, as Buildroot will create
>    it as a symbolic link to '/usr/bin'. In such a situation, should the
> -  overlay have any program, they should be placed in '/usr/bin'.
> +  overlay have any programs, they should be placed in '/usr/bin'.
>  +
>  As shown in xref:customize-dir-structure[], the recommended path for
>    this overlay is +board/<company>/<boardname>/rootfs-overlay+.
> -- 
> 2.39.5
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-11-13 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 20:32 [Buildroot] [PATCH] docs/manual: fix typo in merged-bin details Peter Korsgaard
2025-11-13 16:41 ` Yann E. MORIN via buildroot [this message]
2025-11-13 20:55   ` Peter Korsgaard

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=aRYKRrNl6nALDwmo@landeda \
    --to=buildroot@buildroot.org \
    --cc=peter@korsgaard.com \
    --cc=yann.morin.1998@free.fr \
    /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