All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add a '-r' option to qmp-shell to print out raw JSON replies
Date: Mon, 20 Aug 2012 19:26:09 +0100	[thread overview]
Message-ID: <20120820182609.GC4801@redhat.com> (raw)
In-Reply-To: <20120820152235.1aed6840@doriath.home>

On Mon, Aug 20, 2012 at 03:22:35PM -0300, Luiz Capitulino wrote:
> On Mon, 20 Aug 2012 15:02:23 +0100
> "Daniel P. Berrange" <berrange@redhat.com> wrote:
> 
> > From: "Daniel P. Berrange" <berrange@redhat.com>
> > 
> > By default, the JSON reply is parsed and the corresponding python
> > object printed on the console. When developing JSON client apps
> > for QEMU though, it is handy to see the raw JSON document instead.
> > Add a '-r' option that will cause the raw JSON to be printed,
> > instead of the parsed object. eg
> 
> Looks good, but depends on the previous patch (which is being discussed).
> 
> Btw, I wonder if we should make this the default, or add -v (instead of
> -r) which would allow for extra verbosity by printing both: the reply
> as read by qmp-shell and the parsed.

I dunno, I feel the current default is reasonable and printing both
would be a bit too verbose for commands with larger output.


Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

      reply	other threads:[~2012-08-20 18:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20 14:02 [Qemu-devel] [PATCH] Add a '-r' option to qmp-shell to print out raw JSON replies Daniel P. Berrange
2012-08-20 18:22 ` Luiz Capitulino
2012-08-20 18:26   ` Daniel P. Berrange [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=20120820182609.GC4801@redhat.com \
    --to=berrange@redhat.com \
    --cc=lcapitulino@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 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.