From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Update Python signal-handling documentation
Date: Mon, 11 Sep 2023 19:03:56 +0300 [thread overview]
Message-ID: <834jk0r91v.fsf@gnu.org> (raw)
In-Reply-To: <20230911152250.3434008-1-tromey@adacore.com> (message from Tom Tromey via Gdb-patches on Mon, 11 Sep 2023 09:22:50 -0600)
> Cc: Tom Tromey <tromey@adacore.com>
> Date: Mon, 11 Sep 2023 09:22:50 -0600
> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
>
> I noticed a typo in the "Basic Python" node, and when fixing it
> realized that the paragraph could use a link to the block_signals
> function. This patch is the result.
Thanks.
> -@code{SIGCHLD} handler.
> +@code{SIGCHLD} handler. When creating a new Python thread, you can
> +use @code{gdb.block_signals} or @code{gdb.Thread} to handle this
> +correctly; @xref{Threading in GDB}.
^^^^^
This should be @pxref or "see @ref"; @xref is only pertinent at the
beginning of a sentence, since it produces a capitalized "See".
OK with that nit fixed.
Approved-By: Eli Zaretskii <eliz@gnu.org>
prev parent reply other threads:[~2023-09-11 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 15:22 Tom Tromey
2023-09-11 16:03 ` 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=834jk0r91v.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).