From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 3/3] iotests: Use -qmp-pretty in 067
Date: Thu, 20 Nov 2014 19:56:16 +0100 [thread overview]
Message-ID: <546E3950.6030407@redhat.com> (raw)
In-Reply-To: <20141120183903.GI9266@noname.redhat.com>
On 20.11.2014 19:39, Kevin Wolf wrote:
> Am 17.11.2014 um 13:31 hat Max Reitz geschrieben:
>> 067 invokes query-block, resulting in a reference output with really
>> long lines (which may pose a problem in email patches and always poses a
>> problem when the output changes, because it is hard to see what has
>> actually changed). Use -qmp-pretty to mitigate this issue.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> Reviewed-by: Eric Blake <eblake@redhat.com>
>> ---
>> tests/qemu-iotests/067 | 2 +-
>> tests/qemu-iotests/067.out | 779 +++++++++++++++++++++++++++++++++++++++++----
>> 2 files changed, 723 insertions(+), 58 deletions(-)
> Hm, when I tried to rebase my query-block patch that adds cache
> information, I noticed that I get a trailing space on every line of the
> JSON dump, which isn't there in this patch. So 'cp 067.out.bad 067.out'
> ended up changing every single line. :-/
>
> Did you postprocess the reference output or do really get it without
> trailing whitespace?
Yes, I post-processed it, because you once complained about me sending
patches with trailing whitespace. :-P
As I wrote in some reply to some reply from Eric on some version of this
patch, QEMU's pretty JSON formatter emits whitespace at the end of some
lines.
Max
next prev parent reply other threads:[~2014-11-20 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 12:31 [Qemu-devel] [PATCH v4 0/3] chardev: Add -qmp-pretty Max Reitz
2014-11-17 12:31 ` [Qemu-devel] [PATCH v4 1/3] " Max Reitz
2014-11-17 12:31 ` [Qemu-devel] [PATCH v4 2/3] iotests: _filter_qmp for pretty JSON output Max Reitz
2014-11-17 16:04 ` Eric Blake
2014-11-17 16:14 ` Max Reitz
2014-11-17 17:06 ` Eric Blake
2014-11-17 12:31 ` [Qemu-devel] [PATCH v4 3/3] iotests: Use -qmp-pretty in 067 Max Reitz
2014-11-20 18:39 ` Kevin Wolf
2014-11-20 18:56 ` Max Reitz [this message]
2014-11-20 19:43 ` Eric Blake
2014-11-20 17:02 ` [Qemu-devel] [PATCH v4 0/3] chardev: Add -qmp-pretty Kevin Wolf
2014-11-28 15:55 ` Markus Armbruster
2014-11-28 17:21 ` Paolo Bonzini
2014-12-02 9:24 ` Max Reitz
2014-12-02 18:17 ` Markus Armbruster
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=546E3950.6030407@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).