From: Roman Zippel <zippel@linux-m68k.org>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] top-level config menu dependencies
Date: Thu, 02 Jan 2003 14:32:36 +0100 [thread overview]
Message-ID: <3E143F74.434AD08B@linux-m68k.org> (raw)
In-Reply-To: 20030101162519.GF15200@louise.pinerecords.com
Hi,
Tomas Szepe wrote:
> While converting the way submenus appear in menuconfig depending on
> their main, parent config option, I stumbled upon certain subsystems
> (such as MTD or IrDA) that should clearly have an on/off switch directly
> in the main menu so that one doesn't have to enter the corresponding
> submenus to even see if they're enabled or disabled.
>
> Since the new kernel configurator would have no problems with such
> a setup, I'm posting this RFC to get the general opinion on whether
> this should be carried on with. I'm willing to create and send in
> the patches.
While all config programs should be able to handle this, it might look a
bit strange. Especially the split view of xconfig relies a bit on the
current organisation of the config data.
My idea to handle this would be to turn e.g.:
menu "Memory Technology Devices (MTD)"
config MTD
tristate "Memory Technology Device (MTD) support"
into something like this:
menuconfig MTD
tristate "Memory Technology Device (MTD) support"
This would give the front ends the most flexibility. The required
changes are quite small, so it should be doable for 2.6. I'm not
completely sure about the syntax yet, but above is the most likely
version.
bye, Roman
next prev parent reply other threads:[~2003-01-02 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 16:25 [RFC] top-level config menu dependencies Tomas Szepe
2003-01-01 16:32 ` John Bradford
2003-01-01 16:42 ` Tomas Szepe
2003-01-02 13:32 ` Roman Zippel [this message]
2003-01-02 19:50 ` Tomas Szepe
2003-01-03 1:45 ` Roman Zippel
2003-01-03 23:46 ` [PATCH] menuconfig support for " Roman Zippel
2003-01-04 4:27 ` Tomas Szepe
2003-01-04 4:53 ` Tomas Szepe
2003-01-04 15:52 ` Menuconfig " Tomas Szepe
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=3E143F74.434AD08B@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
--cc=torvalds@transmeta.com \
/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