From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] Query supported notifications by qSupported
Date: Wed, 18 Dec 2013 14:11:00 -0000 [thread overview]
Message-ID: <52B1ACFD.6020507@redhat.com> (raw)
In-Reply-To: <1386856184-16519-2-git-send-email-yao@codesourcery.com>
On 12/12/2013 01:49 PM, Yao Qi wrote:
>
> --> qSupported:XXX;notifications=N1,N2.N3
> (GDB supports notification N1, N2 and N3)
> <-- XXX;Notifications=N1,N2,N4
> (GDBsever supports notification N1, N2 and N4)
But is there any real benefit to the extra "Notifications="
indirection, rather than just treat notifications as regular
qSupported features? IOW, why not simply:
--> qSupported:XXX;N1+;N2+;N3+;N2ext+;ultimatefeature+
?
I.e., GDB supports XXX; N1 notifications; N2 notifications;
N3 notifications; foo extension on N2 notifications;
and the "ultimatefeature" feature, which actually
implies support for 3 different notifications.)
--
Pedro Alves
next prev parent reply other threads:[~2013-12-18 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 13:51 [PATCH 0/4 V7] MI notification on trace started/stopped Yao Qi
2013-12-12 13:51 ` [PATCH 1/4] Query supported notifications by qSupported Yao Qi
2013-12-18 14:11 ` Pedro Alves [this message]
2013-12-19 7:22 ` Yao Qi
2013-12-12 13:51 ` [PATCH 2/4] async remote notification 'Trace' Yao Qi
2013-12-12 13:51 ` [PATCH 3/4] MI notification on trace started/stopped:basic Yao Qi
2013-12-12 13:51 ` [PATCH 4/4] MI notification on trace stop: triggered by remote Yao Qi
2013-12-18 14:09 ` [PATCH 0/4 V7] MI notification on trace started/stopped Pedro Alves
2013-12-19 6:50 ` Yao Qi
2013-12-20 13:57 ` Pedro Alves
2013-12-21 12:50 ` 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=52B1ACFD.6020507@redhat.com \
--to=palves@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).