All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Han Han <hhan@redhat.com>,
	qemu-devel@nongnu.org,
	"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
	Kevin Wolf <kwolf@redhat.com>
Subject: Re: [PATCH] qemu-img.texi: Describe data_file and data_file_raw
Date: Fri, 18 Oct 2019 09:13:56 -0500	[thread overview]
Message-ID: <adf045c3-895c-ccc4-8cf8-1fd2ead496f1@redhat.com> (raw)
In-Reply-To: <20191018095924.4409-1-hhan@redhat.com>

[cc qemu-block]

On 10/18/19 4:59 AM, Han Han wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1763105
> 
> Signed-off-by: Han Han <hhan@redhat.com>
> ---
>   qemu-img.texi | 10 ++++++++++
>   1 file changed, 10 insertions(+)
> 

Reviewed-by: Eric Blake <eblake@redhat.com>

> diff --git a/qemu-img.texi b/qemu-img.texi
> index b5156d6316..44596c2d93 100644
> --- a/qemu-img.texi
> +++ b/qemu-img.texi
> @@ -763,6 +763,16 @@ file which is COW and has data blocks already, it couldn't be changed to NOCOW
>   by setting @code{nocow=on}. One can issue @code{lsattr filename} to check if
>   the NOCOW flag is set or not (Capital 'C' is NOCOW flag).
>   
> +@item data_file
> +File name of data file that is stored in the image and used as a default for
> +opening the image. If the option is used, qcow2 file only stores the metadata
> +of the image.
> +
> +@item data_file_raw
> +This option requires @option{data_file}. If this option is set to @code{on},
> +qemu will always keep the external data file consistent as a standalone
> +read-only raw image. Default value is @code{off}.
> +
>   @end table
>   
>   @item Other
> 

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org


  reply	other threads:[~2019-10-18 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  9:59 [PATCH] qemu-img.texi: Describe data_file and data_file_raw Han Han
2019-10-18 14:13 ` Eric Blake [this message]
2019-10-18 20:58 ` John Snow
2019-10-21  1:06   ` Han Han

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=adf045c3-895c-ccc4-8cf8-1fd2ead496f1@redhat.com \
    --to=eblake@redhat.com \
    --cc=hhan@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 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.