From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [RCF 0/6 V2] MI notification of command option change
Date: Fri, 27 Jul 2012 15:23:00 -0000 [thread overview]
Message-ID: <1343402543-665-1-git-send-email-yao@codesourcery.com> (raw)
Hi,
This is the V2 of this patch set. Compared with V1, some decisions
are made:
1. Keep the command-registration functions unchanged (discard
my xxx_wit_notif functions).
2. Don't emit option change of all gdb commands. We have to
set 'reporting' commands via function 'set_cmd_notify', otherwise
commands are still 'no-reporting'. I believe that frontends will
request more and more options changes, but changes of some gdb
options are useless to frontends. It is noisy to send all option
changes.
Tom and Pedro's review comments are addressed in this version.
next reply other threads:[~2012-07-27 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 15:23 Yao Qi [this message]
2012-07-27 15:23 ` [PATCH 3/6] notify in enum_cmd and scheduler-locking Yao Qi
2012-07-27 15:23 ` [PATCH 6/6] code indentation Yao Qi
2012-07-27 15:23 ` [PATCH 2/6] attach to command_option-changed observer Yao Qi
2012-07-27 17:20 ` Tom Tromey
2012-07-27 17:44 ` Tom Tromey
2012-07-27 15:23 ` [PATCH 1/6] new observer command_option_changed Yao Qi
2012-07-27 17:56 ` Tom Tromey
2012-07-27 15:23 ` [PATCH 4/6] notify in boolean_cmd and circular-trace-buffer Yao Qi
2012-07-27 15:23 ` [PATCH 5/6] notify in string_cmd and trace-notes Yao Qi
2012-07-27 17:07 ` [RCF 0/6 V2] MI notification of command option change Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2012-07-27 14:06 Yao Qi
2012-07-27 14:15 ` 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=1343402543-665-1-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.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