From: Fam Zheng <famz@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC 2/3] qemu-img: Add --unsafe-read option to subcommands
Date: Thu, 20 Apr 2017 11:27:56 +0800 [thread overview]
Message-ID: <20170420032756.GA24486@lemon.lan> (raw)
In-Reply-To: <0f1ecad6-9e85-39a2-6d52-5481f7e309cb@redhat.com>
On Tue, 04/18 08:20, Eric Blake wrote:
> bool, please. (Just because existing code is lousy with using an int
> for a bool doesn't mean we should perpetuate it)
OK, will fix.
>
>
> > @@ -3033,6 +3085,9 @@ static int img_rebase(int argc, char **argv)
> > case OPTION_IMAGE_OPTS:
> > image_opts = true;
> > break;
> > + case 'U':
> > + unsafe_read = 1;
>
> s/1/true/
>
> Good patch, but missing documentation updates to --help/man page. So,
> as encouragement to add that when you drop the RFC, I'll withhold my R-b
> until then. ;)
Yes, I'll add another patch for ease of review.
Fam
next prev parent reply other threads:[~2017-04-20 3:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 2:39 [Qemu-devel] [PATCH RFC 0/3] block: Backdoor to skip image locking in qemu-io/qemu-img Fam Zheng
2017-03-14 2:39 ` [Qemu-devel] [PATCH RFC 1/3] block: Introduce BDRV_O_UNSAFE_READ Fam Zheng
2017-04-18 13:15 ` Eric Blake
2017-03-14 2:39 ` [Qemu-devel] [PATCH RFC 2/3] qemu-img: Add --unsafe-read option to subcommands Fam Zheng
2017-04-18 13:20 ` Eric Blake
2017-04-20 3:27 ` Fam Zheng [this message]
2017-03-14 2:39 ` [Qemu-devel] [PATCH RFC 3/3] qemu-io: Add --unsafe-read option Fam Zheng
2017-04-18 13:27 ` Eric Blake
2017-04-20 3:29 ` Fam Zheng
2017-04-14 1:14 ` [Qemu-devel] [Qemu-block] [PATCH RFC 0/3] block: Backdoor to skip image locking in qemu-io/qemu-img John Snow
2017-04-14 2:25 ` Fam Zheng
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=20170420032756.GA24486@lemon.lan \
--to=famz@redhat.com \
--cc=eblake@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.