From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Florian Larysch <fl@n621.de>
Cc: buildroot@buildroot.org, "Jan Čermák" <sairon@sairon.cz>
Subject: Re: [Buildroot] [PATCH 1/1] fs: erofs: reword "all-fragments" Kconfig text
Date: Sun, 13 Jul 2025 15:49:26 +0200 [thread overview]
Message-ID: <2a135167eacdbdb7f092f42e8904c98d@free.fr> (raw)
In-Reply-To: <20250713125521.18543-1-fl@n621.de>
On 13/07/2025 14:55, Florian Larysch wrote:
> Currently, both BR2_TARGET_ROOTFS_EROFS_ALL_FRAGMENTS and
> BR2_TARGET_ROOTFS_EROFS_FRAGMENTS have the same Kconfig prompt, making
> them hard to distinguish.
>
> Reword the one for -Eall-fragments to be distinct.
>
> Signed-off-by: Florian Larysch <fl@n621.de>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-07-13 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 12:55 [Buildroot] [PATCH 1/1] fs: erofs: reword "all-fragments" Kconfig text Florian Larysch
2025-07-13 13:49 ` Julien Olivain via buildroot [this message]
2025-07-17 20:21 ` Arnout Vandecappelle via buildroot
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=2a135167eacdbdb7f092f42e8904c98d@free.fr \
--to=buildroot@buildroot.org \
--cc=fl@n621.de \
--cc=ju.o@free.fr \
--cc=sairon@sairon.cz \
/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