From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: "Eric S. Raymond" <esr@snark.thyrsus.com>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2 1.0.0 release announcement
Date: Thu, 12 Apr 2001 10:57:33 +0200 [thread overview]
Message-ID: <20010412105733.E25536@pcep-jamie.cern.ch> (raw)
In-Reply-To: <200104101047.f3AAl0h07395@snark.thyrsus.com> <200104120709.f3C798Y426000@saturn.cs.uml.edu>
In-Reply-To: <200104120709.f3C798Y426000@saturn.cs.uml.edu>; from acahalan@cs.uml.edu on Thu, Apr 12, 2001 at 03:09:08AM -0400
Albert D. Cahalan wrote:
> > * All three interfaces do progressive disclosure -- the user only sees
> > questions he/she needs to answer (no more hundreds of greyed-out menu
> > entries for irrelevant drivers!).
>
> Well, that sucks. The greyed-out menu entries were the only good
> thing about xconfig. Such entries provide a clue that you need
> to enable something else to get the feature you desire. Otherwise
> you might figure that the feature is missing, or that you have
> overlooked it.
I agree. I use menuconfig and it's pretty good, but sometimes I miss
the ability to go through all the available options and decide, one by
one, whether I want to enable the option.
Of course if I do not enable some PCI NIC driver, I do not need to see
special options for that driver. That's good. On the other hand, if I
am looking to enable RED, I won't realise that I need to enable
traffic shaping first to discover the RED option.
-- Jamie
next prev parent reply other threads:[~2001-04-12 8:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 10:47 CML2 1.0.0 release announcement Eric S. Raymond
2001-04-10 12:14 ` Russell King
2001-04-11 19:43 ` davej
2001-04-11 20:04 ` Christoph Hellwig
2001-04-11 20:16 ` Dave Jones
2001-04-11 20:27 ` Christoph Hellwig
2001-04-11 22:23 ` Alan Cox
2001-04-11 23:19 ` esr
2001-04-11 23:30 ` Alan Cox
2001-04-11 23:33 ` Alan Cox
2001-04-12 0:45 ` esr
[not found] ` <3AD4FC54.C86AACBE@mandrakesoft.com>
2001-04-12 1:28 ` esr
2001-04-12 1:43 ` CML2 1.0.0 doesn't remember configuration changes jeff millar
2001-04-12 2:50 ` esr
2001-04-12 5:35 ` jeff millar
2001-04-12 2:06 ` esr
2001-04-12 21:20 ` Ingo Oeser
2001-04-14 2:11 ` Eric S. Raymond
2001-04-14 2:29 ` Jeff Garzik
2001-04-14 4:33 ` Nicolas Pitre
2001-04-12 10:45 ` CML2 1.0.0 release announcement Alan Cox
2001-04-11 22:20 ` esr
2001-04-12 7:09 ` Albert D. Cahalan
2001-04-12 8:57 ` Jamie Lokier [this message]
2001-04-12 10:57 ` esr
[not found] <fa.i13tmhv.9kga3t@ifi.uio.no>
[not found] ` <fa.g0offov.1jmmkh9@ifi.uio.no>
2001-04-12 8:50 ` Giacomo Catenazzi
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=20010412105733.E25536@pcep-jamie.cern.ch \
--to=lk@tantalophile.demon.co.uk \
--cc=acahalan@cs.uml.edu \
--cc=esr@snark.thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).