From: Kashyap Chamarthy <kchamart@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com,
qemu-block@nongnu.org, eblake@redhat.com,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 0/3] qemu-img: Document --force-share / -U
Date: Fri, 9 Feb 2018 14:58:09 +0100 [thread overview]
Message-ID: <20180209135807.7gugj2hxxknc7fdo@eukaryote> (raw)
In-Reply-To: <20180209052915.12855-1-famz@redhat.com>
On Fri, Feb 09, 2018 at 01:29:12PM +0800, Fam Zheng wrote:
> v7: Tweak wording again "allowing concurrent writers" -> "allowing other QEMU
> processes to open it in write mode". [Eric, Stefan, Kevin]
> Add patch to document share-rw. [Stefan]
>
> v6: Tweak wording ("concurrent writers"). [Max]
>
> Fam Zheng (3):
> qemu-img.texi: Clean up parameter list
> qemu-img: Document --force-share / -U
> docs: Document share-rw property more thoroughly
>
> docs/qemu-block-drivers.texi | 10 ++++++
> qemu-img.texi | 74 ++++++++++++++++++++++++++++----------------
> 2 files changed, 57 insertions(+), 27 deletions(-)
Thanks!
Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
--
/kashyap
next prev parent reply other threads:[~2018-02-09 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 5:29 [Qemu-devel] [PATCH v7 0/3] qemu-img: Document --force-share / -U Fam Zheng
2018-02-09 5:29 ` [Qemu-devel] [PATCH v7 1/3] qemu-img.texi: Clean up parameter list Fam Zheng
2018-02-09 5:29 ` [Qemu-devel] [PATCH v7 2/3] qemu-img: Document --force-share / -U Fam Zheng
2018-02-09 5:29 ` [Qemu-devel] [PATCH v7 3/3] docs: Document share-rw property more thoroughly Fam Zheng
2018-02-09 10:14 ` [Qemu-devel] [PATCH v7 0/3] qemu-img: Document --force-share / -U Stefan Hajnoczi
2018-02-09 13:58 ` Kashyap Chamarthy [this message]
2018-02-09 14:47 ` Kevin Wolf
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=20180209135807.7gugj2hxxknc7fdo@eukaryote \
--to=kchamart@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).