From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36721) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dddgn-0002gO-71 for qemu-devel@nongnu.org; Fri, 04 Aug 2017 10:35:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dddga-0001xu-Ln for qemu-devel@nongnu.org; Fri, 04 Aug 2017 10:34:57 -0400 Date: Fri, 4 Aug 2017 22:34:07 +0800 From: Fam Zheng Message-ID: <20170804143407.GC14780@lemon> References: <20170804135545.28266-1-famz@redhat.com> <301cd265-7c95-e9da-7c30-e3c342bbae54@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <301cd265-7c95-e9da-7c30-e3c342bbae54@redhat.com> Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] qemu-img: Clarify about relative backing file options List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: qemu-devel@nongnu.org, Kevin Wolf , qemu-block@nongnu.org, Max Reitz On Fri, 08/04 09:23, Eric Blake wrote: > > +If a relative path name is given, the backing file is looked up against > > +@var{filename}, rather than the current working directory. > > Maybe better as: > the backing file is looked up relative to the directory containing > @var{filename} Sounds good, will update.