From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] iotests: Print full path of bad output if mismatch
Date: Fri, 15 Sep 2017 20:30:56 +0800 [thread overview]
Message-ID: <20170915123056.GL17199@lemon> (raw)
In-Reply-To: <20170915121634.GC4077@localhost.localdomain>
On Fri, 09/15 14:16, Kevin Wolf wrote:
> Am 15.09.2017 um 07:45 hat Fam Zheng geschrieben:
> > So it is easier to copy paste the path.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
>
> I don't think I ever tried to do anything with the diff that would have
> required the full path, but if you say so... :-)
>
> Thanks, applied to the block branch.
Thanks.
I often create a new reference output or fix an old one by
cp /x/y/z.out.bad tests/qemu-iotests/???.out
and either the /x/y/z or the path to QEMU repo is some typing if from
out-of-tree build, so getting it from the output of check is handy..
Fam
next prev parent reply other threads:[~2017-09-15 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 5:45 [Qemu-devel] [PATCH] iotests: Print full path of bad output if mismatch Fam Zheng
2017-09-15 12:16 ` Kevin Wolf
2017-09-15 12:30 ` Fam Zheng [this message]
2017-09-15 18:13 ` Eric Blake
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=20170915123056.GL17199@lemon \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).