From: Luiz Capitulino <lcapitulino@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, kchamart@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/4] scripts: qmp-shell: add transaction support
Date: Thu, 23 Apr 2015 09:11:18 -0400 [thread overview]
Message-ID: <20150423091118.628c5878@redhat.com> (raw)
In-Reply-To: <5537F615.7010404@redhat.com>
On Wed, 22 Apr 2015 15:27:17 -0400
John Snow <jsnow@redhat.com> wrote:
>
>
> On 04/22/2015 12:21 PM, John Snow wrote:
> > The qmp-shell is a little rudimentary, but it can be hacked
> > to give us some transactional support without too much difficulty.
> >
> > (1) Prep.
> > (2) Add support for serializing json arrays
> > (3) Allow users to use 'single quotes' instead of "double quotes"
> > (4) Add a special transaction( ... ) syntax that lets users
> > build up transactional commands using the existing qmp shell
> > syntax to define each action.
> > (5) Add a verbose flag to display generated QMP commands.
> >
> > The parsing is not as robust as one would like, but this suffices
> > without adding a proper parser.
> >
> > Design considerations:
> >
> > (1) Try not to disrupt the existing design of the qmp-shell. The existing
> > API is not disturbed.
> >
> > (2) Pick a "magic token" such that it could not be confused for legitimate
> > QMP/JSON syntax. Parentheses are used for this purpose.
> >
> > ===
> > v2:
> > ===
> >
> > - Squash patches 2 & 3:
> > - Remove wholesale replacement of single quotes, in favor of try blocks
> > that attempt to parse as pure JSON, then as Python.
> > - Factored out the value parser block to accomplish the above.
> > - Allow both true/True and false/False for values.
> > - Fix typo in patch 3 cover letter. (was patch 4.)
> >
> > John Snow (4):
> > scripts: qmp-shell: refactor helpers
> > scripts: qmp-shell: Expand support for QMP expressions
> > scripts: qmp-shell: add transaction subshell
> > scripts: qmp-shell: Add verbose flag
> >
> > scripts/qmp/qmp-shell | 125 ++++++++++++++++++++++++++++++++++++++------------
> > 1 file changed, 95 insertions(+), 30 deletions(-)
> >
>
> Version "2+" with the hotfix added, with R-B's added:
> https://github.com/jnsnow/qemu/commits/qmp-shell-plus
>
> To whomever would pull this into their tree: Let me know if you prefer I
> send a "v3" instead.
Please, re-send.
prev parent reply other threads:[~2015-04-23 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 16:21 [Qemu-devel] [PATCH v2 0/4] scripts: qmp-shell: add transaction support John Snow
2015-04-22 16:21 ` [Qemu-devel] [PATCH v2 1/4] scripts: qmp-shell: refactor helpers John Snow
2015-04-22 16:21 ` [Qemu-devel] [PATCH v2 2/4] scripts: qmp-shell: Expand support for QMP expressions John Snow
2015-04-22 16:41 ` John Snow
2015-04-22 17:18 ` Eric Blake
2015-04-22 17:25 ` Eric Blake
2015-04-22 17:33 ` John Snow
2015-04-22 16:21 ` [Qemu-devel] [PATCH v2 3/4] scripts: qmp-shell: add transaction subshell John Snow
2015-04-22 16:21 ` [Qemu-devel] [PATCH v2 4/4] scripts: qmp-shell: Add verbose flag John Snow
2015-04-22 19:27 ` [Qemu-devel] [PATCH v2 0/4] scripts: qmp-shell: add transaction support John Snow
2015-04-23 13:11 ` 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=20150423091118.628c5878@redhat.com \
--to=lcapitulino@redhat.com \
--cc=jsnow@redhat.com \
--cc=kchamart@redhat.com \
--cc=qemu-devel@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 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).