From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: "Fiona Klute \(WIWA\)" <fiona.klute@gmx.de>,
Brandon Maier <Brandon.Maier@collins.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3] docs/manual: use space-separated list for BR2_EXTERNAL
Date: Thu, 5 Sep 2024 22:17:03 +0200 [thread overview]
Message-ID: <20240905221703.2c85a70e@windsurf> (raw)
In-Reply-To: <ZtoM6k0EaDsZa4mV@landeda>
On Thu, 5 Sep 2024 21:56:26 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> The thing is that all the other lists are space-separated:
> BR2_ROOTFS_DEVICE_TABLE
> BR2_ROOTFS_STATIC_DEVICE_TABLE
> BR2_TARGET_TZ_ZONELIST
> BR2_ROOTFS_USERS_TABLES
> BR2_ROOTFS_OVERLAY
> BR2_ROOTFS_PRE_BUILD_SCRIPT
> BR2_ROOTFS_POST_BUILD_SCRIPT
> BR2_ROOTFS_POST_FAKEROOT_SCRIPT
> BR2_ROOTFS_POST_IMAGE_SCRIPT
>
> The list goes on and on, notably the options to specify the lists of
> .config fragments for the kernel, uclibc, uboot etc...
I agree, but these are Buildroot menuconfig options, not something
passed on the command line.
That being said, it's a matter of taste, so I will not oppose to the
change.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-09-05 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 20:53 [Buildroot] [PATCH v3] docs/manual: use space-separated list for BR2_EXTERNAL Yann E. MORIN
2024-09-05 19:35 ` Thomas Petazzoni via buildroot
2024-09-05 19:56 ` Yann E. MORIN
2024-09-05 20:17 ` Thomas Petazzoni via buildroot [this message]
2024-09-06 7:32 ` 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=20240905221703.2c85a70e@windsurf \
--to=buildroot@buildroot.org \
--cc=Brandon.Maier@collins.com \
--cc=fiona.klute@gmx.de \
--cc=thomas.petazzoni@bootlin.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