From: Max Reitz <mreitz@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img: Fix documentation of convert
Date: Mon, 15 May 2017 19:29:09 +0200 [thread overview]
Message-ID: <d5702e65-8c1b-35b3-6670-a2e344cdfb9c@redhat.com> (raw)
In-Reply-To: <20170515103551.31313-1-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
On 2017-05-15 12:35, Fam Zheng wrote:
> It got lost in commit a8d16f9ca "qemu-img: Update documentation for -U".
>
> Reported-by: Max Reitz <mreitz@redhat.com>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> qemu-img-cmds.hx | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Thanks!
Applied to my block branch:
https://github.com/XanClic/qemu/commits/block
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 498 bytes --]
prev parent reply other threads:[~2017-05-15 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 10:35 [Qemu-devel] [PATCH] qemu-img: Fix documentation of convert Fam Zheng
2017-05-15 14:22 ` Eric Blake
2017-05-15 17:29 ` Max Reitz [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=d5702e65-8c1b-35b3-6670-a2e344cdfb9c@redhat.com \
--to=mreitz@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@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).