From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] targets: move target options to their own sub-menu
Date: Fri, 16 Aug 2013 01:10:30 +0200 [thread overview]
Message-ID: <520D5FE6.2090007@mind.be> (raw)
In-Reply-To: <1376598482-9492-1-git-send-email-yann.morin.1998@free.fr>
On 15/08/13 22:28, Yann E. MORIN wrote:
> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
>
> Currently, all target options lie in the top-level menu.
> This looks a bit clumsy, since all other options are neatly
> folded into their own sematic sub-menus each.
>
> Move the target option into their own sub-menu too.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
> arch/Config.in | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/Config.in b/arch/Config.in
> index 0b5b218..640926a 100644
> --- a/arch/Config.in
> +++ b/arch/Config.in
> @@ -1,3 +1,5 @@
> +menu "Target options"
I completely agree with the idea - especially in the xconfig, the big
list of architecture options is extremely annoying. However, the menu
title is not very clear. How about "Target architecture selection"? Or maybe
Target CPU architecture
Target CPU architecture family
Target CPU architecture variant
Regards,
Arnout
> +
> config BR2_ARCH_IS_64
> bool
>
> @@ -324,3 +326,5 @@ endif
> if BR2_xtensa
> source "arch/Config.in.xtensa"
> endif
> +
> +endmenu # Target options
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-08-15 23:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 20:28 [Buildroot] [PATCH] targets: move target options to their own sub-menu Yann E. MORIN
2013-08-15 23:10 ` Arnout Vandecappelle [this message]
2013-08-16 6:30 ` Thomas De Schampheleire
2013-08-16 6:39 ` Yann E. MORIN
2013-08-16 10:24 ` Thomas De Schampheleire
2013-08-16 10:30 ` Thomas De Schampheleire
2013-08-16 17:59 ` Yann E. MORIN
2013-08-16 19:04 ` Thomas De Schampheleire
2013-08-18 16:41 ` Thomas Petazzoni
2013-08-19 16:33 ` Arnout Vandecappelle
2013-08-18 7:24 ` Thomas De Schampheleire
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=520D5FE6.2090007@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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