From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] boot: get rid of toplevel submenus
Date: Mon, 19 Sep 2011 08:54:29 +0200 [thread overview]
Message-ID: <87vcsp58ey.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110919084606.7ff12ec8@skate> (Thomas Petazzoni's message of "Mon, 19 Sep 2011 08:46:06 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> Sub options are indented anyway, so no need for empty menus / force
>> people to enter sub menus to see configuration options.
Thomas> My preference was the old way. Even if suboptions are indented, I
Thomas> think it's a mess in menuconfig to have the U-Boot suboptions in the
Thomas> middle of the bootloader list.
I find the empty submenus when E.G. u-boot isn't enabled pretty ugly,
and use of a normal config is by far the most used option - E.G:
git grep '^menuconfig '|wc -l
10
Out of ~700 packages, bootloaders, filesystems, ..
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-09-19 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 20:09 [Buildroot] [git commit] boot: get rid of toplevel submenus Peter Korsgaard
2011-09-19 6:46 ` Thomas Petazzoni
2011-09-19 6:54 ` Peter Korsgaard [this message]
2011-09-19 7:07 ` Thomas Petazzoni
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=87vcsp58ey.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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