From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Karel Kulhavy <clock@twibright.com>
Cc: linux-kernel@vger.kernel.org, akpm <akpm@osdl.org>
Subject: [PATCH] clarify menuconfig /(search) help text
Date: Fri, 23 Sep 2005 19:09:06 -0700 [thread overview]
Message-ID: <20050923190906.5e0d721f.rdunlap@xenotime.net> (raw)
In-Reply-To: <20050914065010.GA8430@kestrel.twibright.com>
From: Randy Dunlap <rdunlap@xenotime.net>
Add explicit text about
- where menuconfig '/' (search) searches for strings,
- that substrings are allowed, and
- that regular expressions are supported.
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
scripts/kconfig/mconf.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
diff -Naurp linux-2614-rc2-git3/scripts/kconfig/mconf.c~search_keyword linux-2614-rc2-git3/scripts/kconfig/mconf.c
--- linux-2614-rc2-git3/scripts/kconfig/mconf.c~search_keyword 2005-08-28 16:41:01.000000000 -0700
+++ linux-2614-rc2-git3/scripts/kconfig/mconf.c 2005-09-23 19:04:39.000000000 -0700
@@ -219,6 +219,7 @@ save_config_help[] = N_(
search_help[] = N_(
"\n"
"Search for CONFIG_ symbols and display their relations.\n"
+ "Regular expressions are allowed.\n"
"Example: search for \"^FOO\"\n"
"Result:\n"
"-----------------------------------------------------------------\n"
@@ -531,7 +532,7 @@ again:
cprint("--title");
cprint(_("Search Configuration Parameter"));
cprint("--inputbox");
- cprint(_("Enter Keyword"));
+ cprint(_("Enter CONFIG_ (sub)string to search for (omit CONFIG_)"));
cprint("10");
cprint("75");
cprint("");
---
prev parent reply other threads:[~2005-09-24 2:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 6:50 Search in make menuconfig doesn't work properly Karel Kulhavy
2005-09-14 9:27 ` Cal Peake
2005-09-14 12:39 ` Karel Kulhavy
2005-09-14 15:07 ` Randy.Dunlap
2005-09-14 14:56 ` Randy.Dunlap
2005-09-24 2:09 ` Randy.Dunlap [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=20050923190906.5e0d721f.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=clock@twibright.com \
--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®