From: "Frederick, Fabian" <Fabian.Frederick@prov-liege.be>
To: "Robert P. J. Day" <rpjday@mindspring.com>,
Bernd Eckenfels <ecki-lkm@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: RE: why the current kernel config menu layout is a mess
Date: Fri, 25 Jul 2003 15:18:08 +0200 [thread overview]
Message-ID: <D9B4591FDBACD411B01E00508BB33C1B01BDE949@mesadm.epl.prov-liege.be> (raw)
from my poking around in the whole Kconfig structure, it seems that the
menu structure is tied awfully closely to the underlying directory
structure. this would make it overly difficult to shift parts of
the config menu around without dragging the corresponding directories
around as well.
<Sources are located regarding programming hierarchy _but_
<relevant Kconfig can tune situation using 'depends' feature
<at ease so that menuconfig, kernelserver ... have an optimized view
<over kernel tree.OTOH a major problem resides in lack of functionnalities
<especially when you don't know where to look at (ie.alphabetical order,
<search engine....I'm adding those functions to kernelServer (wconf) ASAP.
next reply other threads:[~2003-07-25 13:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 13:18 Frederick, Fabian [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-25 15:53 why the current kernel config menu layout is a mess John Bradford
2003-07-25 15:28 John Bradford
2003-07-25 14:58 John Bradford
2003-07-25 15:07 ` Roman Zippel
2003-07-25 15:26 ` Robert P. J. Day
2003-07-25 15:51 ` Tomas Szepe
2003-07-25 16:11 ` Herbert Pötzl
2003-07-25 0:56 Robert P. J. Day
2003-07-25 1:27 ` Bernd Eckenfels
2003-07-25 12:46 ` Robert P. J. Day
2003-07-25 14:10 ` 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=D9B4591FDBACD411B01E00508BB33C1B01BDE949@mesadm.epl.prov-liege.be \
--to=fabian.frederick@prov-liege.be \
--cc=ecki-lkm@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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;
as well as URLs for NNTP newsgroup(s).