From: Eli Zaretskii <eliz@gnu.org>
To: Christina Schimpe <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] gdb, doc: correct argument description for info connections/inferiors
Date: Mon, 27 Mar 2023 16:47:11 +0300 [thread overview]
Message-ID: <83a5zy9uhs.fsf@gnu.org> (raw)
In-Reply-To: <20230327113922.618826-2-christina.schimpe@intel.com> (message from Christina Schimpe via Gdb-patches on Mon, 27 Mar 2023 13:39:22 +0200)
> Cc: Christina Schimpe <christina.schimpe@intel.com>
> Date: Mon, 27 Mar 2023 13:39:22 +0200
> From: Christina Schimpe via Gdb-patches <gdb-patches@sourceware.org>
>
> From: Nils-Christian Kempke <nils-christian.kempke@intel.com>
>
> It said for 'info inferiors' and 'info connections' that the argument
> could be 'a space separated list of inferior numbers' which is correct
> but incomplete. In fact the arguments can be any space separated
> combination of numbers and (ascending) ranges.
>
> The beginning of the section now describes the ID list as a new keyword.
>
> Co-Authored-By: Christina Schimpe <christina.schimpe@intel.com>
> ---
> gdb/doc/gdb.texinfo | 23 ++++++++++++++++-------
> 1 file changed, 16 insertions(+), 7 deletions(-)
Thanks. The text is OK, but please drop the cross-references (and the
@anchor which you created for them): you actually allude to stuff
described in the same node, and not very far before the referencing
text, so cross-references are inappropriate. Instead, says "(see
above)", or even nothing at all, since the reader just have read about
ID lists, and there's an index entry for that if the reader forgot.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2023-03-27 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 11:39 [PATCH 0/1] Correct " Christina Schimpe
2023-03-27 11:39 ` [PATCH 1/1] gdb, doc: correct " Christina Schimpe
2023-03-27 13:47 ` Eli Zaretskii [this message]
2023-03-30 16:59 ` Schimpe, Christina
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=83a5zy9uhs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=christina.schimpe@intel.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).