From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: why the new config process is a *big* step backwards
Date: Mon, 13 Jan 2003 10:37:51 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0301131037270.26506-100000@dell> (raw)
In-Reply-To: <20030113153212.GB12500@louise.pinerecords.com>
On Mon, 13 Jan 2003, Tomas Szepe wrote:
> Robert,
>
> please study scripts/kconfig/*, not how one particular frontend is.
> The new kernel configurator is actually a big improvement over the
> traditional stuff we used to have up to 2.4. Okay, it is a fact that
> xconfig is far from great, but that doesn't matter -- the important
> thing is Kconfig provides a clean, generic system for the actual kernel
> configuration. As I already pointed out a fortnight ago or so, the
> only config frontend likely to stay in linux.tar in the long run is
> menuconfig, serving as a reference to userland people who are certain
> to come up with heaps of different Kconfig frontends (that is when
> 2.6 ships I guess).
>
> If you need a nifty graphical frontend right away, I suggest you
> go ahead and write the first off-tree xconfig.
ok, point taken. i'll take a look at it, thanks.
rday
next prev parent reply other threads:[~2003-01-13 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 13:26 why the new config process is a *big* step backwards Robert P. J. Day
2003-01-13 15:32 ` Tomas Szepe
2003-01-13 15:37 ` Robert P. J. Day [this message]
2003-01-13 16:32 ` Werner Almesberger
2003-01-13 22:09 ` Roman Zippel
2002-01-14 19:18 ` Romain Lievin
[not found] <20030113134017$1d68@gated-at.bofh.it>
2003-01-14 20:46 ` Kai Henningsen
2003-01-16 11:47 ` David Woodhouse
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.44.0301131037270.26506-100000@dell \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.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).