From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Mike Day <ncmike@ncultra.org>,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Add backing file option to qemu-img create help.
Date: Mon, 12 May 2014 09:20:00 -0600 [thread overview]
Message-ID: <5370E6A0.3030406@redhat.com> (raw)
In-Reply-To: <20140512151356.GC4371@noname.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On 05/12/2014 09:13 AM, Kevin Wolf wrote:
> Am 12.05.2014 um 17:05 hat Eric Blake geschrieben:
>> On 05/12/2014 06:35 AM, Mike Day wrote:
>>> For the create subcommand the backing file (-b) option is documented
>>> on-line but not in the binary. Add it.
Online where? In 'qemu-img --help', or on some web page (at what URL)?
>> is -o considered to be preferred over -b, as an explanation for why it
>> is not documented?
>
> Yes, it is. -b was documented before -o backing_file existed. Commit
> 8063d0fe removed it.
If anything, that says we need to fix whatever "documented on-line"
source was documenting something that we want to be obsolete; and maybe
tweak qemu-img to be verbose about warning on the use of deprecated
options. But this patch would go in the wrong direction of reviving
intentionally undocumented code.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-05-12 15:25 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 [this message]
2014-05-12 15:36 ` Mike Day
2014-05-12 15:53 ` Eric Blake
2014-05-12 16:05 ` Mike Day
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=5370E6A0.3030406@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=ncmike@ncultra.org \
--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).