public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christina Schimpe <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/1] gdb, doc: correct argument description for info connections/inferiors
Date: Thu, 30 Mar 2023 21:12:51 +0300	[thread overview]
Message-ID: <838rfe3y70.fsf@gnu.org> (raw)
In-Reply-To: <20230330180239.3217030-2-christina.schimpe@intel.com> (message from Christina Schimpe on Thu, 30 Mar 2023 20:02:39 +0200)

> From: Christina Schimpe <christina.schimpe@intel.com>
> Cc: eliz@gnu.org,
> 	Christina Schimpe <christina.schimpe@intel.com>
> Date: Thu, 30 Mar 2023 20:02:39 +0200
> 
> 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 | 19 +++++++++++++------
>  1 file changed, 13 insertions(+), 6 deletions(-)

Thanks, this is OK.

Approved-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2023-03-30 18:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 18:02 [PATCH v2 0/1] Correct " Christina Schimpe
2023-03-30 18:02 ` [PATCH v2 1/1] gdb, doc: correct " Christina Schimpe
2023-03-30 18:12   ` Eli Zaretskii [this message]
2023-04-11 16:51     ` 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=838rfe3y70.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).