From: Luiz Capitulino <lcapitulino@redhat.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Trivial fix for QMP/qmp-events.txt
Date: Mon, 18 Oct 2010 12:12:58 -0200 [thread overview]
Message-ID: <20101018121258.78774b7c@doriath> (raw)
In-Reply-To: <4CB653F6.100@jp.fujitsu.com>
On Thu, 14 Oct 2010 09:51:02 +0900
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> wrote:
> Fix example of STOP event that was just copy-and-pasted.
>
> Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Applied to the QMP queue, thanks.
> ---
> QMP/qmp-events.txt | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt
> index 01ec85f..aa20210 100644
> --- a/QMP/qmp-events.txt
> +++ b/QMP/qmp-events.txt
> @@ -89,7 +89,7 @@ Data: None.
>
> Example:
>
> -{ "event": "SHUTDOWN",
> +{ "event": "STOP",
> "timestamp": { "seconds": 1267041730, "microseconds": 281295 } }
>
> VNC_CONNECTED
prev parent reply other threads:[~2010-10-18 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 0:51 [Qemu-devel] [PATCH] Trivial fix for QMP/qmp-events.txt Hidetoshi Seto
2010-10-18 14:12 ` Luiz Capitulino [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=20101018121258.78774b7c@doriath \
--to=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seto.hidetoshi@jp.fujitsu.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 NNTP newsgroup(s).