From: John Bradford <john@grabjohn.com>
To: szepe@pinerecords.com (Tomas Szepe)
Cc: linux-kernel@vger.kernel.org
Subject: Re: a few more "make xconfig" inconsistencies
Date: Wed, 1 Jan 2003 15:24:36 +0000 (GMT) [thread overview]
Message-ID: <200301011524.h01FOaZ6001581@darkstar.example.net> (raw)
In-Reply-To: <20030101151107.GN14184@louise.pinerecords.com> from "Tomas Szepe" at Jan 01, 2003 04:11:07 PM
> > > Oh, I see what you mean. This behavior is a "feature" of the old
> > > xconfig (it's been so since the 2.0 times or thereabouts). menuconfig
> > > will hide entirely what xconfig merely grays out.
> >
> > I actually like that feature :-(.
> >
> > On the other hand, the TCL-based config system has gone completely in
> > 2.5. I look forward to the 2.7 tree opening when hopefully somebody
> > will bring it back as an extra choice, just for the sake of it :-).
>
> The new config system provides a generic library for handling kernel
> configuration. My bet is we can expect lots of kernel config frontends
> turning up as soon as 2.6 sees the light of the world (and people find
> out how great it is :D).
Cool - the big disadvantage of the QT-based kernel configurator is
that it takes ages to load on slow boxes, (even on my MMX-200 it's
slow, and that's not _that_ old).
John.
next prev parent reply other threads:[~2003-01-01 15:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 14:05 a few more "make xconfig" inconsistencies Robert P. J. Day
2003-01-01 14:16 ` Tomas Szepe
2003-01-01 14:32 ` Robert P. J. Day
2003-01-01 14:45 ` John Bradford
2003-01-01 14:49 ` Robert P. J. Day
2003-01-01 14:57 ` Robert P. J. Day
2003-01-01 14:51 ` Tomas Szepe
2003-01-01 15:04 ` John Bradford
2003-01-01 15:11 ` Tomas Szepe
2003-01-01 15:24 ` John Bradford [this message]
2003-01-01 15:21 ` John Bradford
2003-01-01 15:24 ` Tomas Szepe
2003-01-01 16:08 ` Bill Davidsen
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=200301011524.h01FOaZ6001581@darkstar.example.net \
--to=john@grabjohn.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