From: Fam Zheng <famz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] iotests: 095: Clean up QEMU before showing image info
Date: Sat, 4 Jun 2016 07:45:27 +0800 [thread overview]
Message-ID: <20160603234527.GA3218@ad.usersys.redhat.com> (raw)
In-Reply-To: <70297268-cb80-f2dd-4d9e-0cbb9b96198c@redhat.com>
On Fri, 06/03 16:52, Max Reitz wrote:
> On 03.06.2016 11:07, Fam Zheng wrote:
> > Somehow in my locking series, I missed this case where concurrent access
> > to an image is performed, perhaps we can remove this case independently.
>
> The patch itself is good, but this commit message will not make much
> sense in the git log. I'd be fine with removing it completely because
> the title itself should be sufficient. (Which is something I can do in
> case you agree.)
Yes, agreed completely. Thanks!
Fam
next prev parent reply other threads:[~2016-06-03 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 9:07 [Qemu-devel] [PATCH] iotests: 095: Clean up QEMU before showing image info Fam Zheng
2016-06-03 14:52 ` Max Reitz
2016-06-03 23:45 ` Fam Zheng [this message]
2016-06-06 11:04 ` Max Reitz
2016-06-06 11:04 ` Max Reitz
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=20160603234527.GA3218@ad.usersys.redhat.com \
--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).