[binutils-gdb] Use upper case for metasyntactic variables in "help find"

[Tom Tromey]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=c763b8943348582e651dda24f88bb9f8db24672b

commit c763b8943348582e651dda24f88bb9f8db24672b
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Feb 14 07:58:58 2019 -0700

    Use upper case for metasyntactic variables in "help find"
    
    While answering a user's question on irc, I realized that the
    metasyntactic variables in "help find" are not in upper case.  As you
    know this is one of my pet quests, so here is a patch to fix this.
    Tested on x86-64 Fedora 29.
    
    gdb/ChangeLog
    2019-02-20  Tom Tromey  <tromey@adacore.com>
    
    	* findcmd.c (_initialize_mem_search): Use upper case for
    	metasyntactic variables.

Diff:
---
 gdb/ChangeLog | 5 +++++
 gdb/findcmd.c | 6 +++---
 2 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 721e636..0341981 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2019-02-20  Tom Tromey  <tromey@adacore.com>
+
+	* findcmd.c (_initialize_mem_search): Use upper case for
+	metasyntactic variables.
+
 2019-02-20  Alan Hayward  <alan.hayward@arm.com>
 
 	* aarch64-tdep.c (aarch64_add_reggroups): New function.
diff --git a/gdb/findcmd.c b/gdb/findcmd.c
index cd46100..52f8f80 100644
--- a/gdb/findcmd.c
+++ b/gdb/findcmd.c
@@ -286,9 +286,9 @@ _initialize_mem_search (void)
   add_cmd ("find", class_vars, find_command, _("\
 Search memory for a sequence of bytes.\n\
 Usage:\nfind \
-[/size-char] [/max-count] start-address, end-address, expr1 [, expr2 ...]\n\
-find [/size-char] [/max-count] start-address, +length, expr1 [, expr2 ...]\n\
-size-char is one of b,h,w,g for 8,16,32,64 bit values respectively,\n\
+[/SIZE-CHAR] [/MAX-COUNT] START-ADDRESS, END-ADDRESS, EXPR1 [, EXPR2 ...]\n\
+find [/SIZE-CHAR] [/MAX-COUNT] START-ADDRESS, +LENGTH, EXPR1 [, EXPR2 ...]\n\
+SIZE-CHAR is one of b,h,w,g for 8,16,32,64 bit values respectively,\n\
 and if not specified the size is taken from the type of the expression\n\
 in the current language.\n\
 Note that this means for example that in the case of C-like languages\n\