From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Daniel Gutson <daniel.gutson@tallertechnologies.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: specifying gdb's exit code
Date: Wed, 23 Apr 2014 17:57:00 -0000 [thread overview]
Message-ID: <5357FF04.2070605@redhat.com> (raw)
In-Reply-To: <87lhuw9br6.fsf@fleche.redhat.com>
On 04/23/2014 06:49 PM, Tom Tromey wrote:
> diff --git a/gdb/cli/cli-cmds.c b/gdb/cli/cli-cmds.c
> index bfcd975..0eff952 100644
> --- a/gdb/cli/cli-cmds.c
> +++ b/gdb/cli/cli-cmds.c
> @@ -1685,7 +1685,11 @@ strict == evaluate script according to filename extension, error if not supporte
> show_script_ext_mode,
> &setlist, &showlist);
>
> - add_com ("quit", class_support, quit_command, _("Exit gdb."));
> + add_com ("quit", class_support, quit_command, _("\
> +Exit gdb.\n\
> +Usage: quit [EXPR]\n\
> +The optional expression EXPR, if present, is evaluated and the result\n\
> +used as gdb's exit code. The default is zero."));
I think this should be "GDB" in caps. "apropos gdb" seems to
indicate that's how we spell it in the online help.
Otherwise looks fine to me.
Thanks,
--
Pedro Alves
next prev parent reply other threads:[~2014-04-23 17:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF5HaEVTZAxc0FNR9GnGNKJqxGSrbQaTfZ7ZRMoueTg6jQyL8A@mail.gmail.com>
[not found] ` <CAF5HaEWDv6Gb2m-iDpzcM4y_ybkT46R1b96xxdS9buLHbsgwRQ@mail.gmail.com>
[not found] ` <CADPb22RS0J3X8hcBiUiDPp62RYiKPE4vCSPV5WEMUF01KzsiLg@mail.gmail.com>
[not found] ` <CAF5HaEV3wMHXfk3jLmbY-E6XAaZSmBRhzDjo2BvhQ7NbvvCtZQ@mail.gmail.com>
2014-04-17 21:52 ` Daniel Gutson
2014-04-22 12:37 ` Daniel Gutson
2014-04-23 17:11 ` Tom Tromey
2014-04-23 17:29 ` Pedro Alves
2014-04-23 17:36 ` Paul_Koning
2014-04-23 17:46 ` Pedro Alves
2014-04-23 17:49 ` Tom Tromey
2014-04-23 17:57 ` Pedro Alves [this message]
2014-04-25 15:44 ` Tom Tromey
2014-04-23 18:17 ` Paul_Koning
2014-04-23 18:23 ` Tom Tromey
2014-04-23 20:53 ` Daniel Gutson
2014-04-23 20:55 ` Daniel Gutson
2014-04-23 17:29 ` Eli Zaretskii
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=5357FF04.2070605@redhat.com \
--to=palves@redhat.com \
--cc=daniel.gutson@tallertechnologies.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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