From: "Wei, Jiangang" <weijg.fnst@cn.fujitsu.com>
To: "famz@redhat.com" <famz@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] block/raw-posix: Fix error_report of mounting message
Date: Fri, 3 Jun 2016 09:56:51 +0000 [thread overview]
Message-ID: <1464947750.5185.47.camel@localhost> (raw)
In-Reply-To: <20160603090019.GA29600@ad.usersys.redhat.com>
On Fri, 2016-06-03 at 17:00 +0800, Fam Zheng wrote:
> On Thu, 06/02 10:46, Wei, Jiangang wrote:
> > My intention is only to avoid the output of multiple location
> > information.
>
> Then I think this should have gone into the commit message.
OK, I'll make more detailed description in next version.
>
> Fam
>
>
prev parent reply other threads:[~2016-06-03 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 7:08 [Qemu-devel] [PATCH] block/raw-posix: Fix error_report of mounting message Wei Jiangang
2016-06-01 7:23 ` Fam Zheng
2016-06-02 3:04 ` Wei, Jiangang
2016-06-02 3:15 ` Fam Zheng
2016-06-02 7:57 ` Markus Armbruster
2016-06-02 10:46 ` Wei, Jiangang
2016-06-03 9:00 ` Fam Zheng
2016-06-03 9:56 ` Wei, Jiangang [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=1464947750.5185.47.camel@localhost \
--to=weijg.fnst@cn.fujitsu.com \
--cc=famz@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).