From: John Bradford <john@grabjohn.com>
To: john@grabjohn.com, zippel@linux-m68k.org
Cc: ecki-lkm@lina.inka.de, Fabian.Frederick@prov-liege.be,
linux-kernel@vger.kernel.org, rpjday@mindspring.com
Subject: RE: why the current kernel config menu layout is a mess
Date: Fri, 25 Jul 2003 16:28:48 +0100 [thread overview]
Message-ID: <200307251528.h6PFSmPQ001169@81-2-122-30.bradfords.org.uk> (raw)
> > Maybe a completely new, out of kernel tree configurator would be worth
> > thinking about, leaving the in-kernel configurator as a legacy option.
> > I know the config system underwent a major overhaul during 2.5, but I
> > think we could go even further.
>
> Maybe you should look first at something before you throw it away?
> Kconfig is already modular, the Kconfig parser is a library, which you can
> easily connect to your favourite script language and then you can do with
> the Kconfig data whatever you want.
Sorry, I meant make the current targets, like menuconfig and xconfig
legacy options, not eliminate the Kconfig parser altogether.
John.
next reply other threads:[~2003-07-25 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 15:28 John Bradford [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 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 13:18 Frederick, Fabian
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=200307251528.h6PFSmPQ001169@81-2-122-30.bradfords.org.uk \
--to=john@grabjohn.com \
--cc=Fabian.Frederick@prov-liege.be \
--cc=ecki-lkm@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=zippel@linux-m68k.org \
/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).