From: Kashyap Chamarthy <kchamart@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-trivial@nongnu.org, mjt@tls.msk.ru, qemu-devel@nongnu.org,
lcapitulino@redhat.com
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] qmp-shell: add documentation
Date: Tue, 28 Jul 2015 09:51:21 +0200 [thread overview]
Message-ID: <20150728075121.GA13890@tesla.redhat.com> (raw)
In-Reply-To: <1435775149-17285-1-git-send-email-jsnow@redhat.com>
On Wed, Jul 01, 2015 at 02:25:49PM -0400, John Snow wrote:
> I should probably document the changes that were made.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> scripts/qmp/qmp-shell | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
Since I did some tests[1] when you wrote these improvements to
qmp-shell, the change looks good, FWIW:
Reviewed-By: Kashyap Chamarthy <kchamart@redhat.com>
[1]
https://lists.nongnu.org/archive/html/qemu-devel/2015-04/msg04201.html
> diff --git a/scripts/qmp/qmp-shell b/scripts/qmp/qmp-shell
> index 65280d2..fa39bf0 100755
> --- a/scripts/qmp/qmp-shell
> +++ b/scripts/qmp/qmp-shell
> @@ -29,6 +29,41 @@
> # (QEMU) device_add driver=e1000 id=net1
> # {u'return': {}}
> # (QEMU)
> +#
> +# key=value pairs also support Python or JSON object literal subset notations,
> +# without spaces. Dictionaries/objects {} are supported as are arrays [].
> +#
> +# example-command arg-name1={'key':'value','obj'={'prop':"value"}}
> +#
> +# Both JSON and Python formatting should work, including both styles of
> +# string literal quotes. Both paradigms of literal values should work,
> +# including null/true/false for JSON and None/True/False for Python.
> +#
> +#
> +# Transactions have the following multi-line format:
> +#
> +# transaction(
> +# action-name1 [ arg-name1=arg1 ] ... [arg-nameN=argN ]
> +# ...
> +# action-nameN [ arg-name1=arg1 ] ... [arg-nameN=argN ]
> +# )
> +#
> +# One line transactions are also supported:
> +#
> +# transaction( action-name1 ... )
> +#
> +# For example:
> +#
> +# (QEMU) transaction(
> +# TRANS> block-dirty-bitmap-add node=drive0 name=bitmap1
> +# TRANS> block-dirty-bitmap-clear node=drive0 name=bitmap0
> +# TRANS> )
> +# {"return": {}}
> +# (QEMU)
> +#
> +# Use the -v and -p options to activate the verbose and pretty-print options,
> +# which will echo back the properly formatted JSON-compliant QMP that is being
> +# sent to QEMU, which is useful for debugging and documentation generation.
>
> import qmp
> import json
> --
> 2.1.0
>
>
--
/kashyap
WARNING: multiple messages have this Message-ID (diff)
From: Kashyap Chamarthy <kchamart@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-trivial@nongnu.org, mjt@tls.msk.ru, qemu-devel@nongnu.org,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qmp-shell: add documentation
Date: Tue, 28 Jul 2015 09:51:21 +0200 [thread overview]
Message-ID: <20150728075121.GA13890@tesla.redhat.com> (raw)
In-Reply-To: <1435775149-17285-1-git-send-email-jsnow@redhat.com>
On Wed, Jul 01, 2015 at 02:25:49PM -0400, John Snow wrote:
> I should probably document the changes that were made.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> scripts/qmp/qmp-shell | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
Since I did some tests[1] when you wrote these improvements to
qmp-shell, the change looks good, FWIW:
Reviewed-By: Kashyap Chamarthy <kchamart@redhat.com>
[1]
https://lists.nongnu.org/archive/html/qemu-devel/2015-04/msg04201.html
> diff --git a/scripts/qmp/qmp-shell b/scripts/qmp/qmp-shell
> index 65280d2..fa39bf0 100755
> --- a/scripts/qmp/qmp-shell
> +++ b/scripts/qmp/qmp-shell
> @@ -29,6 +29,41 @@
> # (QEMU) device_add driver=e1000 id=net1
> # {u'return': {}}
> # (QEMU)
> +#
> +# key=value pairs also support Python or JSON object literal subset notations,
> +# without spaces. Dictionaries/objects {} are supported as are arrays [].
> +#
> +# example-command arg-name1={'key':'value','obj'={'prop':"value"}}
> +#
> +# Both JSON and Python formatting should work, including both styles of
> +# string literal quotes. Both paradigms of literal values should work,
> +# including null/true/false for JSON and None/True/False for Python.
> +#
> +#
> +# Transactions have the following multi-line format:
> +#
> +# transaction(
> +# action-name1 [ arg-name1=arg1 ] ... [arg-nameN=argN ]
> +# ...
> +# action-nameN [ arg-name1=arg1 ] ... [arg-nameN=argN ]
> +# )
> +#
> +# One line transactions are also supported:
> +#
> +# transaction( action-name1 ... )
> +#
> +# For example:
> +#
> +# (QEMU) transaction(
> +# TRANS> block-dirty-bitmap-add node=drive0 name=bitmap1
> +# TRANS> block-dirty-bitmap-clear node=drive0 name=bitmap0
> +# TRANS> )
> +# {"return": {}}
> +# (QEMU)
> +#
> +# Use the -v and -p options to activate the verbose and pretty-print options,
> +# which will echo back the properly formatted JSON-compliant QMP that is being
> +# sent to QEMU, which is useful for debugging and documentation generation.
>
> import qmp
> import json
> --
> 2.1.0
>
>
--
/kashyap
next prev parent reply other threads:[~2015-07-28 14:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 18:25 [Qemu-trivial] [PATCH] qmp-shell: add documentation John Snow
2015-07-01 18:25 ` [Qemu-devel] " John Snow
2015-07-02 15:31 ` [Qemu-trivial] " Luiz Capitulino
2015-07-02 15:31 ` [Qemu-devel] " Luiz Capitulino
2015-07-07 16:33 ` [Qemu-trivial] " John Snow
2015-07-07 16:33 ` John Snow
2015-07-23 7:36 ` [Qemu-trivial] " Markus Armbruster
2015-07-23 7:36 ` Markus Armbruster
2015-07-27 3:30 ` [Qemu-trivial] " John Snow
2015-07-27 3:30 ` John Snow
2015-07-27 21:59 ` [Qemu-trivial] " Eric Blake
2015-07-27 21:59 ` Eric Blake
2015-07-30 14:48 ` [Qemu-trivial] " Luiz Capitulino
2015-07-30 14:48 ` Luiz Capitulino
2015-08-05 9:49 ` [Qemu-trivial] " Markus Armbruster
2015-08-05 9:49 ` Markus Armbruster
2015-07-28 7:51 ` Kashyap Chamarthy [this message]
2015-07-28 7:51 ` Kashyap Chamarthy
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=20150728075121.GA13890@tesla.redhat.com \
--to=kchamart@redhat.com \
--cc=jsnow@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.