From: John Bradford <john@grabjohn.com>
To: rpjday@mindspring.com (Robert P. J. Day)
Cc: linux-kernel@vger.kernel.org
Subject: Re: inconsistent xconfig menu for "Wirless LAN (non-hamradio)"
Date: Sun, 5 Jan 2003 13:02:01 +0000 (GMT) [thread overview]
Message-ID: <200301051302.h05D21DT001147@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0301050737500.18541-100000@dell> from "Robert P. J. Day" at Jan 05, 2003 07:45:12 AM
> since that card uses the hermes chipset, i naturally selected
> "Hermes chipset 802.11b ...". but wait -- a few lines down, there's
> a comment, "Wireless Pcmcia/Cardbus cards support." strange, i
> could have sworn i selected something like that a few lines up
> already.
In my opinion, options like that should be called "Generic Hermes
chipset 802.11b support".
> worse, even further down, there's "Hermes PCMCIA card support,"
> for which the original selection has help that tells me that it was
> necessary for me to select this later feature. in that case,
> if it's *required*, i shouldn't have any freedom -- the config
> should select it for me.
No, there might be a reason not to have options selected which are
"required", and that needs to be possible whichever kernel
configurator is being used.
> anyway, you the idea -- for my poor, little LinkSys WFC-11 card,
> there are too many selections in that menu that seem to apply to me,
> some of which should be more tightly related, or subsumed in a
> submenu.
The *best* thing to do is to make the help text more helpful, because
that way it explains the configuration to the user, instead of just
doing it for them.
John.
next prev parent reply other threads:[~2003-01-05 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 12:45 Robert P. J. Day
2003-01-05 13:02 ` John Bradford [this message]
2003-01-05 18:56 ` Robert P. J. Day
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=200301051302.h05D21DT001147@darkstar.example.net \
--to=john@grabjohn.com \
--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
Powered by JetHome