qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mike Day <ncmike@ncultra.org>
To: Eric Blake <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Add backing file option to qemu-img create help.
Date: Mon, 12 May 2014 12:05:10 -0400	[thread overview]
Message-ID: <CAGaKXu0MuNktSgQMdfZ-keeHFi=V5JjRrvBJw7Dvnt5-4RW1aQ@mail.gmail.com> (raw)
In-Reply-To: <5370EE94.8090703@redhat.com>

On Mon, May 12, 2014 at 11:53 AM, Eric Blake <eblake@redhat.com> wrote:
> Ah, but it is:
>
> $ qemu-img create -f qcow2 -o help
> Supported options:
> size             Virtual disk size
> compat           Compatibility level (0.10 or 1.1)
> backing_file     File name of a base image
> backing_fmt      Image format of the base image
> encryption       Encrypt the image
> cluster_size     qcow2 cluster size
> preallocation    Preallocation mode (allowed values: off, metadata)
> lazy_refcounts   Postpone refcount updates
>
> and more importantly, it only appears in the help output of -f modes
> that actually support a backing file.  Contrast:
>
> $ qemu-img create -f raw -o help
> Supported options:
> size             Virtual disk size

This is much more prominent in the top-level help:

rebase [-q] [-f fmt] [-t cache] [-p] [-u] -b backing_file [-F
backing_fmt] filename

  reply	other threads:[~2014-05-12 16:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 12:35 [Qemu-devel] [PATCH] Add backing file option to qemu-img create help Mike Day
2014-05-12 15:05 ` Eric Blake
2014-05-12 15:13   ` Kevin Wolf
2014-05-12 15:20     ` Eric Blake
2014-05-12 15:36       ` Mike Day
2014-05-12 15:53         ` Eric Blake
2014-05-12 16:05           ` Mike Day [this message]
2014-05-12 16:32             ` Eric Blake
2014-05-12 16:36               ` Kevin Wolf
2014-05-12 17:02                 ` Eric Blake
2014-05-13  8:46                   ` Kevin Wolf
2014-05-12 17:10                 ` Mike Day

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='CAGaKXu0MuNktSgQMdfZ-keeHFi=V5JjRrvBJw7Dvnt5-4RW1aQ@mail.gmail.com' \
    --to=ncmike@ncultra.org \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).