From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] Make entries in the "Device drivers" menu individually selectable
Date: Mon, 18 Dec 2006 10:31:31 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612181024090.26607@localhost.localdomain> (raw)
In-Reply-To: <4586AD83.5030600@s5r6.in-berlin.de>
On Mon, 18 Dec 2006, Stefan Richter wrote:
> Robert P. J. Day wrote:
> [...]
> > in any event, as i mentioned earlier, i'm just trying to find a
> > way to make the menu entries more obvious and more easily
> > selectable, without having to enter each submenu to see what it
> > represents.
> [...]
>
> Yes, this and the points you made in the other post are definitely
> valid.
this is a long-term suggestion, but the easiest solution might be to
introduce a new kbuild directive: "selectablemenu" or something like
that, with a form similar to:
=================
selectablemenu ISDN
bool "ISDN support"
config ...
config ...
config ...
endmenu
=================
the top level entry would be just a yes/no toggle as to whether you
want that support in general, and the internal entries would represent
the submenu and all of them would *automatically* depend on the top
config entry (in this case, ISDN). and the "help" entry could be
available from that top-level entry without having to enter the
submenu. as opposed to what you need to do now.
i'm guessing that structure would be sufficient for 90% of the
current menu layouts. just a thought.
rday
prev parent reply other threads:[~2006-12-18 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 8:31 Robert P. J. Day
2006-12-16 10:52 ` Stefan Richter
2006-12-16 17:58 ` Jan Engelhardt
2006-12-18 9:38 ` Robert P. J. Day
2006-12-18 9:50 ` Robert P. J. Day
2006-12-18 15:02 ` Stefan Richter
2006-12-18 15:31 ` Robert P. J. Day [this message]
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=Pine.LNX.4.64.0612181024090.26607@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®