Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] [gdb/doc]: clarify the language for the '?' packet
Date: Wed, 16 Dec 2020 21:18:08 +0200	[thread overview]
Message-ID: <83k0th8sr3.fsf@gnu.org> (raw)
In-Reply-To: <20201216182332.15456-1-alex.bennee@linaro.org> (message from Alex =?utf-8?Q?Benn=C3=A9e?= via Gdb-patches on Wed, 16 Dec 2020 18:23:32 +0000)

> Date: Wed, 16 Dec 2020 18:23:32 +0000
> From: Alex Bennée via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Alex Bennée <alex.bennee@linaro.org>
> 
> 2020-12-16  Alex Bennée <alex.bennee@linaro.org>
> 
> 	* doc/gdb.texinfo: add clarifying language for ? packet

Please indicate in what node the change is being made (in parentheses,
as if the node were a function).

> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -39493,9 +39493,10 @@ The remote target both supports and has enabled extended mode.
>  @item ?
>  @cindex @samp{?} packet
>  @anchor{? packet}
> -Indicate the reason the target halted.  The reply is the same as for
> -step and continue.  This packet has a special interpretation when the
> -target is in non-stop mode; see @ref{Remote Non-Stop}.
> +This is sent when connection is first established to query the reason
> +the target halted.  The reply is the same as for step and continue.
> +This packet has a special interpretation when the target is in
> +non-stop mode; see @ref{Remote Non-Stop}.

This is OK, thanks.

      reply	other threads:[~2020-12-16 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 18:23 Alex Bennée via Gdb-patches
2020-12-16 19:18 ` Eli Zaretskii via Gdb-patches [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=83k0th8sr3.fsf@gnu.org \
    --to=gdb-patches@sourceware.org \
    --cc=alex.bennee@linaro.org \
    --cc=eliz@gnu.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