Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>, Mike Frysinger <vapier@gentoo.org>,
	       Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v3] gdb: improve usage strings
Date: Thu, 23 Aug 2012 16:45:00 -0000	[thread overview]
Message-ID: <50365E25.3050906@redhat.com> (raw)
In-Reply-To: <50360FCB.5030707@redhat.com>

On 08/23/2012 12:11 PM, Pedro Alves wrote:
> On 08/14/2012 06:34 PM, Doug Evans wrote:
>>>
>>>    c = add_com ("signal", class_run, signal_command, _("\
>>> -Continue program giving it signal specified by the argument.\n\
>>> -An argument of \"0\" means continue program without giving it a signal."));
>>> +Continue program with the specified signal.\n\
>>> +Usage: signal SIGNAL\n\
>>> +The SIGNAL arugment is processed the same as the handle command.\n\
>                ^^^^^^^^
> 
> Typo.

Fixed.

2012-08-23  Pedro Alves  <palves@redhat.com>

	* infcmd.c (_initialize_infcmd) <signal command>: Fix typo in help
	string.

---

 gdb/infcmd.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/infcmd.c b/gdb/infcmd.c
index 8300182..9d43193 100644
--- a/gdb/infcmd.c
+++ b/gdb/infcmd.c
@@ -3019,7 +3019,7 @@ all targets."));
   c = add_com ("signal", class_run, signal_command, _("\
 Continue program with the specified signal.\n\
 Usage: signal SIGNAL\n\
-The SIGNAL arugment is processed the same as the handle command.\n\
+The SIGNAL argument is processed the same as the handle command.\n\
 \n\
 An argument of \"0\" means continue the program without sending it a signal.\n\
 This is useful in cases where the program stopped because of a signal,\n\


      reply	other threads:[~2012-08-23 16:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-11 16:55 [PATCH] " Mike Frysinger
2012-08-11 17:16 ` Eli Zaretskii
2012-08-11 17:36   ` Mike Frysinger
2012-08-11 17:52     ` Eli Zaretskii
2012-08-11 18:08       ` Mike Frysinger
2012-08-14 15:08         ` Tom Tromey
2012-08-12  5:06     ` Doug Evans
2012-08-12  5:10       ` Mike Frysinger
2012-08-12 17:35       ` Eli Zaretskii
2012-08-13  2:06 ` [PATCH v2] " Mike Frysinger
2012-08-13 20:29   ` Doug Evans
2012-08-14  5:13     ` Mike Frysinger
2012-08-23 11:11     ` Pedro Alves
2012-08-14  5:29 ` [PATCH v3] " Mike Frysinger
2012-08-14 17:34   ` Doug Evans
2012-08-14 18:10     ` Eli Zaretskii
2012-08-15  1:58       ` Mike Frysinger
2012-08-15  7:22         ` Regression for gdb.base/help.exp [Re: [PATCH v3] gdb: improve usage strings] Jan Kratochvil
2012-08-15 16:25           ` Mike Frysinger
2012-08-15 16:27             ` Doug Evans
2012-08-20  4:29             ` Sergio Durigan Junior
2012-08-17  3:06           ` Mike Frysinger
2012-08-23 16:26         ` further improve "handle" help string Pedro Alves
2012-08-23 16:44           ` Eli Zaretskii
2012-08-23 17:18           ` Mike Frysinger
2012-08-23 17:38             ` Pedro Alves
2012-08-23 11:11     ` [PATCH v3] gdb: improve usage strings Pedro Alves
2012-08-23 16:45       ` Pedro Alves [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=50365E25.3050906@redhat.com \
    --to=palves@redhat.com \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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