From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Per-inferior thread IDs
Date: Tue, 15 Dec 2015 19:39:00 -0000 [thread overview]
Message-ID: <8337v333id.fsf@gnu.org> (raw)
In-Reply-To: <1450206316-25680-1-git-send-email-palves@redhat.com> (message from Pedro Alves on Tue, 15 Dec 2015 19:05:16 +0000)
> From: Pedro Alves <palves@redhat.com>
> Date: Tue, 15 Dec 2015 19:05:16 +0000
>
> +See @xref{Convenience Vars,, Convenience Variables}, for general
Either "See @ref" or just "@xref" (which will produce "See").
Other than that, the documentation parts are OK, with one comment: it
seems confusing to talk about "per-inferior ID" when evidently you
refer to the 2.3 form of the thread ID. Can we find some other term
for this ID?
Thanks.
next prev parent reply other threads:[~2015-12-15 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 19:05 Pedro Alves
2015-12-15 19:39 ` Eli Zaretskii [this message]
2015-12-17 13:17 ` Pedro Alves
2015-12-17 16:54 ` Eli Zaretskii
2015-12-18 18:11 ` Pedro Alves
2015-12-18 19:36 ` Eli Zaretskii
2015-12-24 14:56 ` [PATCH] thread ID ranges (Per-inferior thread IDs) Pedro Alves
2015-12-24 16:24 ` Eli Zaretskii
2015-12-18 17:53 ` [PATCH] Per-inferior thread IDs Joel Brobecker
2015-12-18 18:47 ` Pedro Alves
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=8337v333id.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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