From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] attach to command_param_changed observer.
Date: Fri, 03 Aug 2012 11:30:00 -0000 [thread overview]
Message-ID: <83lihwb4bp.fsf@gnu.org> (raw)
In-Reply-To: <1343992904-9375-3-git-send-email-yao@codesourcery.com>
> From: Yao Qi <yao@codesourcery.com>
> Date: Fri, 3 Aug 2012 19:21:43 +0800
>
> 'mi_suppress_breakpoint_notifications' is used to suppress mi
> breakpoint notifications. This patch is to change this variable
> to an array so that multiple mi notifications can be suppressed.
> The following patch will use it to suppress other MI notifications.
>
> This patch is to attach function 'mi_command_param_changed' to
> observer 'command_param_changed', so that a MI notification
> "=cmd-param-changed" is sent to MI frontend. If the command param
> change is requested from MI, the notification is suppressed.
>
> Compared with V2, V3 has the following changes,
>
> - Rename MI notification to "=cmd-param-changed".
> - Update doc especially for multi-word commands.
> - Rename some functions from "optoin" to "param".
OK for the documentation parts.
Thanks.
next prev parent reply other threads:[~2012-08-03 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 11:22 [RCF 0/3 V3] MI notification of command parameter change Yao Qi
2012-08-03 11:22 ` [PATCH 3/3] test case Yao Qi
2012-08-03 17:37 ` Tom Tromey
2012-08-06 15:48 ` Yao Qi
2012-08-06 20:21 ` Tom Tromey
2012-08-03 11:22 ` [PATCH 1/3] new observer command_param_changed Yao Qi
2012-08-03 17:35 ` Tom Tromey
2012-08-06 15:44 ` Yao Qi
2012-08-06 20:21 ` Tom Tromey
2012-08-07 2:58 ` Yao Qi
2012-08-08 18:11 ` Tom Tromey
2012-08-03 11:22 ` [PATCH 2/3] attach to command_param_changed observer Yao Qi
2012-08-03 11:30 ` Eli Zaretskii [this message]
2012-08-03 17:36 ` Tom Tromey
2012-08-10 0:57 ` [committed]: [RCF 0/3 V3] MI notification of command parameter change 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=83lihwb4bp.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