From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qemu-img: Clarify about relative backing file options
Date: Fri, 4 Aug 2017 09:42:59 -0500 [thread overview]
Message-ID: <0cf16030-d5d0-6e7e-8fc7-88abd8f6d3ca@redhat.com> (raw)
In-Reply-To: <20170804143658.23020-1-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On 08/04/2017 09:36 AM, Fam Zheng wrote:
> It's not too surprising when a user specifies the backing file relative
> to the current working directory instead of the top layer image. This
> causes error when they differ. Though the error message has enough
> information to infer the fact about the misunderstanding, it is better
> if we document this explicitly, so that users don't have to learn from
> mistakes.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
>
> ---
> v2: Improve wording. [Eric]
> ---
> qemu-img.texi | 9 +++++++++
> 1 file changed, 9 insertions(+)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-04 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 14:36 [Qemu-devel] [PATCH v2] qemu-img: Clarify about relative backing file options Fam Zheng
2017-08-04 14:42 ` Eric Blake [this message]
2017-08-04 15:14 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2017-08-08 10:14 ` Stefan Hajnoczi
2017-08-31 6:52 ` [Qemu-devel] " Fam Zheng
2017-09-07 15:11 ` 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=0cf16030-d5d0-6e7e-8fc7-88abd8f6d3ca@redhat.com \
--to=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 \
/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).