From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/5] Add annex in a async remote notification.
Date: Tue, 22 Jan 2013 08:06:00 -0000 [thread overview]
Message-ID: <83fw1tod6e.fsf@gnu.org> (raw)
In-Reply-To: <1358838232-13319-2-git-send-email-yao@codesourcery.com>
> From: Yao Qi <yao@codesourcery.com>
> Date: Tue, 22 Jan 2013 15:03:48 +0800
>
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -38604,13 +38604,15 @@ transmit notifications without fear of confusing older clients. There
> are no notifications defined for @value{GDBN} to send at the moment, but we
> assume that most older stubs would ignore them, as well.)
>
> -Each notification is comprised of three parts:
> +Each notification is comprised of four parts:
> @table @samp
> -@item @var{name}:@var{event}
> +@item @var{name}[:@var{annex}]:@var{event}
Is it a good idea to have the optional part in the middle? If there
are MI clients out there that support the previous form, they might
now confuse ANNEX to be an EVENT.
The documentation patch in this changeset is OK with me.
next prev parent reply other threads:[~2013-01-22 8:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 7:05 [PATCH 0/5] MI notification on trace started/stopped (V3) Yao Qi
2013-01-22 7:05 ` [PATCH 1/5] Add annex in a async remote notification Yao Qi
2013-01-22 8:06 ` Eli Zaretskii [this message]
2013-02-16 3:40 ` Yao Qi
2013-02-16 9:27 ` Eli Zaretskii
2013-03-29 17:17 ` Yao Qi
2013-03-31 0:39 ` Eli Zaretskii
2013-01-22 7:05 ` [PATCH 3/5] async remote notification 'Trace' Yao Qi
2013-01-22 8:06 ` Eli Zaretskii
2013-01-22 7:05 ` [PATCH 2/5] Query supported notifications by qSupported Yao Qi
2013-01-22 8:09 ` Eli Zaretskii
2013-01-22 8:41 ` Yao Qi
2013-01-22 10:26 ` Eli Zaretskii
2013-01-22 7:06 ` [PATCH 5/5] MI notification on trace stop: triggered by remote Yao Qi
2013-01-22 7:06 ` [PATCH 4/5] MI notification on trace started/stopped:basic Yao Qi
2013-01-22 8:11 ` Eli Zaretskii
2013-01-30 4:00 ` [ping]: [PATCH 0/5] MI notification on trace started/stopped (V3) Yao Qi
2013-02-07 12:41 ` [ping 2]: " Yao Qi
2013-02-16 4:01 ` [PATCH 0/5] MI notification on trace started/stopped (V3.1) Yao Qi
2013-02-16 4:01 ` [PATCH 1/5] Add annex in a async remote notification Yao Qi
2013-02-16 9:27 ` Eli Zaretskii
2013-02-16 4:02 ` [PATCH 5/5] MI notification on trace stop: triggered by remote Yao Qi
2013-02-16 4:02 ` [PATCH 4/5] MI notification on trace started/stopped:basic Yao Qi
2013-02-16 9:36 ` Eli Zaretskii
2013-02-16 4:02 ` [PATCH 3/5] async remote notification 'Trace' Yao Qi
2013-02-16 9:34 ` Eli Zaretskii
2013-02-16 4:02 ` [PATCH 2/5] Query supported notifications by qSupported Yao Qi
2013-02-16 9:33 ` Eli Zaretskii
2013-03-11 9:26 ` Yao Qi
2013-03-11 16:59 ` Eli Zaretskii
2013-02-25 3:14 ` ping: [PATCH 0/5] MI notification on trace started/stopped (V3.1) Yao Qi
2013-03-04 2:34 ` ping^2 : " Yao Qi
2013-04-02 2:33 ` [PATCH v4 0/5] MI notification on trace started/stopped Yao Qi
2013-04-02 3:15 ` [PATCH 2/5] Query supported notifications by qSupported Yao Qi
2013-04-02 3:58 ` [PATCH 3/5] async remote notification 'Trace' Yao Qi
2013-04-02 12:46 ` [PATCH 5/5] MI notification on trace stop: triggered by remote Yao Qi
2013-04-02 13:07 ` [PATCH 4/5] MI notification on trace started/stopped:basic Yao Qi
2013-04-02 13:30 ` [PATCH 1/5] Add annex in a async remote notification Yao Qi
2013-04-10 15:46 ` [PATCH v4 0/5] MI notification on trace started/stopped Yao Qi
2013-04-17 14:37 ` [ping 2]: " Yao Qi
2013-04-18 15:16 ` Pedro Alves
2013-04-18 16:14 ` Yao Qi
2013-06-04 9:20 ` Yao Qi
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=83fw1tod6e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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