From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [RFA 06/12] Update help text in dcache.c
Date: Mon, 30 Apr 2018 14:37:00 -0000 [thread overview]
Message-ID: <20180430143731.30007-7-tom@tromey.com> (raw)
In-Reply-To: <20180430143731.30007-1-tom@tromey.com>
This updates some text in dcache.c to follow GNU standards.
Here, I found a couple of spots needing an update.
2018-04-29 Tom Tromey <tom@tromey.com>
* dcache.c (dcache_info_1): Update usage text.
(_initialize_dcache): Update help text.
---
gdb/ChangeLog | 5 +++++
gdb/dcache.c | 7 ++++---
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/gdb/dcache.c b/gdb/dcache.c
index 805f492bd7..20b781fa01 100644
--- a/gdb/dcache.c
+++ b/gdb/dcache.c
@@ -595,7 +595,7 @@ dcache_info_1 (DCACHE *dcache, const char *exp)
i = strtol (exp, &linestart, 10);
if (linestart == exp || i < 0)
{
- printf_filtered (_("Usage: info dcache [linenumber]\n"));
+ printf_filtered (_("Usage: info dcache [LINENUMBER]\n"));
return;
}
@@ -701,9 +701,10 @@ exists only for compatibility reasons."),
add_info ("dcache", info_dcache_command,
_("\
Print information on the dcache performance.\n\
+Usage: info dcache [LINENUMBER]\n\
With no arguments, this command prints the cache configuration and a\n\
-summary of each line in the cache. Use \"info dcache <lineno> to dump\"\n\
-the contents of a given line."));
+summary of each line in the cache. With an argument, dump\"\n\
+the contents of the given line."));
add_prefix_cmd ("dcache", class_obscure, set_dcache_command, _("\
Use this command to set number of lines in dcache and line-size."),
--
2.13.6
next prev parent reply other threads:[~2018-04-30 14:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 14:37 [RFA 00/12] Small help text tweaks Tom Tromey
2018-04-30 14:37 ` [RFA 12/12] Update help text in record.c Tom Tromey
2018-05-04 18:57 ` Pedro Alves
2018-04-30 14:37 ` [RFA 02/12] Update help strings in skip.c Tom Tromey
2018-05-04 18:09 ` Pedro Alves
2018-04-30 14:37 ` [RFA 01/12] Fix help and documentation for inferior commands Tom Tromey
2018-04-30 15:26 ` Eli Zaretskii
2018-05-04 18:07 ` Pedro Alves
2018-05-09 20:29 ` Tom Tromey
2018-05-10 9:17 ` Eli Zaretskii
2018-04-30 14:37 ` [RFA 08/12] Update help text in disasm.c Tom Tromey
2018-05-04 18:54 ` Pedro Alves
2018-04-30 14:37 ` Tom Tromey [this message]
2018-05-04 18:27 ` [RFA 06/12] Update help text in dcache.c Pedro Alves
2018-04-30 14:37 ` [RFA 05/12] Update help strings in TUI Tom Tromey
2018-05-04 18:26 ` Pedro Alves
2018-04-30 14:37 ` [RFA 09/12] Update help text in tracepoint.c Tom Tromey
2018-05-04 18:54 ` Pedro Alves
2018-04-30 14:37 ` [RFA 07/12] Update help text for "jump" command Tom Tromey
2018-05-04 18:52 ` Pedro Alves
2018-04-30 14:37 ` [RFA 03/12] Update core-related help strings Tom Tromey
2018-05-04 18:11 ` Pedro Alves
2018-05-09 20:31 ` Tom Tromey
2018-05-24 21:28 ` Pedro Alves
2018-04-30 14:37 ` [RFA 11/12] Update help text in linux-fork.c Tom Tromey
2018-05-04 18:56 ` Pedro Alves
2018-04-30 14:37 ` [RFA 10/12] Update help text in record-btrace.c Tom Tromey
2018-05-04 18:55 ` Pedro Alves
2018-04-30 14:37 ` [RFA 04/12] Update memattr.c help strings Tom Tromey
2018-05-04 18:16 ` Pedro Alves
2018-05-09 20:35 ` Tom Tromey
2018-05-24 17:53 ` Pedro Alves
2018-04-30 14:40 ` [RFA 00/12] Small help text tweaks Eli Zaretskii
2018-04-30 15:13 ` Tom Tromey
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=20180430143731.30007-7-tom@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.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