From: Roman Zippel <zippel@linux-m68k.org>
To: Dominik Brodowski <linux@brodo.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: menucofig[2.5.56] bug: help texts in "choice"
Date: Sat, 11 Jan 2003 15:50:43 +0100 [thread overview]
Message-ID: <3E202F43.E51FB502@linux-m68k.org> (raw)
In-Reply-To: 20030110220402.GA1909@brodo.de
Hi,
Dominik Brodowski wrote:
> In 2.5.56 I'm seeing a bug in "make menuconfig" on x86: selecting "processor
> type and features", then "processor family", and then "help" for any entry,
> I always get "There is no help available for this kernel option." even
> though there are extensive help texts in arch/i386/Kconfig.
Move the help text from CONFIG_M386 entry to the choice entry. I didn't
do this automatically since often the help text has to splitted
manually. It's on my TODO list, but I still hope someone else would like
to do this. :)
BTW menuconfig will only show the general help text. Showing the
individual help text entries would require changing lxdialog, what I
tried to avoid so far (so it's even lower on my TODO list).
bye, Roman
prev parent reply other threads:[~2003-01-11 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 22:04 menucofig[2.5.56] bug: help texts in "choice" Dominik Brodowski
2003-01-11 14:50 ` Roman Zippel [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=3E202F43.E51FB502@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
/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