From: Sam Ravnborg <sam@ravnborg.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Roman Zippel <zippel@linux-m68k.org>
Subject: Re: why don't top-level menu entries have help info?
Date: Mon, 7 May 2007 22:28:13 +0200 [thread overview]
Message-ID: <20070507202813.GA20680@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705071548240.29393@localhost.localdomain>
Added Roman Zippel to cc - he is kconfig maintainer,
Sam
On Mon, May 07, 2007 at 03:54:13PM -0400, Robert P. J. Day wrote:
>
> i'd be surprised if this hasn't come up before, but would it be hard
> to add a facility to Kconfig so that "menu" entries have some help
> info?
>
> after i run "make menuconfig" and i'm sitting at the main menu,
> there's nothing to help me out in understanding what any of those
> choices might mean.
>
> i might see "Instrumentation Support" and wonder just what that is,
> but if i ask for help (which is, as you can see, clearly available
> at the bottom of the config screen), i get nothing meaningful, just
> the generic README.
>
> i think it would be helpful if those entries also supported help
> info. just my $0.02.
>
> rday
>
> --
> ========================================================================
> Robert P. J. Day
> Linux Consulting, Training and Annoying Kernel Pedantry
> Waterloo, Ontario, CANADA
>
> http://fsdev.net/wiki/index.php?title=Main_Page
> ========================================================================
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2007-05-07 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 19:54 Robert P. J. Day
2007-05-07 20:28 ` Sam Ravnborg [this message]
2007-05-08 8:50 ` Jan Engelhardt
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=20070507202813.GA20680@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=zippel@linux-m68k.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®