mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jochen Hein <jochen@jochen.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.48] Config.help misleading
Date: Wed, 20 Nov 2002 17:54:26 +0100	[thread overview]
Message-ID: <87zns4chbx.fsf@gswi1164.jochen.org> (raw)
In-Reply-To: <200211181823.gAIIN1eA002882@pool-151-204-203-202.delv.east.verizon.net> (Skip Ford's message of "Mon, 18 Nov 2002 19:30:17 +0100")

Skip Ford <skip.ford@verizon.net> writes:

> Jochen Hein wrote:
>> Help says to say "Y" if unsure, but that isn't allowed:
>> ,----
>> |   UHCI HCD (most Intel and VIA) support (USB_UHCI_HCD) [N/m/?] (NEW) ?
>> | 
> [snip]
>> | 133). If unsure, say Y.
>> | 
>> |   UHCI HCD (most Intel and VIA) support (USB_UHCI_HCD) [N/m/?] (NEW) y
>> `----
>
> Did you choose to make USB support a module?  

Yes.

> If you said 'y' to USB
> support, then you should have a 'y' option above.  However, you most
> likely said 'm' for USB support so 'm' is all you can do for this
> because it depends on it.  Had you said 'n' to USB support, you wouldn't
> be able to select 'y' or 'm' for the above.

So, what should the help text say?  I propose
"If unsure, say M".
That should get it right more often than the current text.
Or perhaps your explanation should be included.  I think that's even
better.  Randy?

Jochen

-- 
Wenn Du nicht weißt was Du tust, tu's mit Eleganz.

      reply	other threads:[~2002-11-21 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18 16:06 Jochen Hein
2002-11-18 18:02 ` Randy.Dunlap
2002-11-18 18:22 ` Skip Ford
2002-11-20 16:54   ` Jochen Hein [this message]

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=87zns4chbx.fsf@gswi1164.jochen.org \
    --to=jochen@jochen.org \
    --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

all inboxes | Powered by JetHome®