From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] qemu-img: Clarify about relative backing file options
Date: Thu, 31 Aug 2017 14:52:57 +0800 [thread overview]
Message-ID: <20170831065257.GA14896@lemon.lan> (raw)
In-Reply-To: <20170804143658.23020-1-famz@redhat.com>
On Fri, 08/04 22:36, 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.
Gentle ping as a reminder for 2.11, as 2.10 is now out of door.
Fam
next prev parent reply other threads:[~2017-08-31 6:53 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
2017-08-04 15:14 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2017-08-08 10:14 ` Stefan Hajnoczi
2017-08-31 6:52 ` Fam Zheng [this message]
2017-09-07 15:11 ` [Qemu-devel] " 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=20170831065257.GA14896@lemon.lan \
--to=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 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.