From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Minor "catch" documentation improvements
Date: Fri, 10 May 2019 13:31:00 -0000 [thread overview]
Message-ID: <83d0kqfncz.fsf@gnu.org> (raw)
In-Reply-To: <20190510131327.14790-1-tromey@adacore.com> (message from Tom Tromey on Fri, 10 May 2019 07:13:27 -0600)
> From: Tom Tromey <tromey@adacore.com>
> Cc: Tom Tromey <tromey@adacore.com>
> Date: Fri, 10 May 2019 07:13:27 -0600
>
> This patch makes a few minor improvements to the catchpoint
> documentation:
>
> * "catch exception" and "catch handlers" now mention the argument in
> the @item.
>
> * "catch exception unhandled" is moved to be closer to "catch
> exception", rather than after "catch handlers".
>
> * "catch load" and "catch unload" now wrap the argument in @var.
>
> gdb/doc/ChangeLog
> 2019-05-10 Tom Tromey <tromey@adacore.com>
>
> * gdb.texinfo (Set Catchpoints): Add text for parameter to "catch
> exception" and "catch handlers". Move "catch exception unhandled"
> text. Use @var for "catch load" and "catch unload"
Thanks, this LGTM.
prev parent reply other threads:[~2019-05-10 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 13:13 Tom Tromey
2019-05-10 13:31 ` Eli Zaretskii [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=83d0kqfncz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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