From: John Snow <jsnow@redhat.com>
To: Max Reitz <mreitz@redhat.com>, Thomas Huth <thuth@redhat.com>,
Eric Blake <eblake@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] using "qemu-img convert -O qcow2" to convert qcow v1 to v2 creates a qcow v3 file?
Date: Tue, 14 Nov 2017 15:30:26 -0500 [thread overview]
Message-ID: <e76811c5-6a5a-cf5e-2571-9e112e609740@redhat.com> (raw)
In-Reply-To: <20253223-df8f-162d-b8c8-dfa56af9fffd@redhat.com>
On 11/14/2017 01:46 PM, Max Reitz wrote:
> On 2017-11-14 19:45, Thomas Huth wrote:
>> On 14.11.2017 14:32, Max Reitz wrote:
>> [...]
>>> Well, do you want to document it? I'd rather deprecate it altogether.
>>
>> Maybe a first step could be to change qemu-img so that it refuses to
>> create new qcow1 images (but still can convert them into other formats).
>> So basically make qcow1 read-only?
>
> Yep, and the actual first step to that is to make it issue a deprecation
> warning when creating qcow v1 images (which is what I proposed). :-)
>
> Max
>
Deprecation warning is good.
In future versions you can shimmy it behind a
--no-really-I-want-this-old-format option, I think we ought to support
creating the images for as long as is technologically convenient.
next prev parent reply other threads:[~2017-11-14 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 17:14 [Qemu-devel] using "qemu-img convert -O qcow2" to convert qcow v1 to v2 creates a qcow v3 file? Peter Maydell
2017-11-13 17:29 ` Peter Maydell
2017-11-13 17:58 ` Eric Blake
2017-11-13 18:08 ` Eric Blake
2017-11-14 13:32 ` Max Reitz
2017-11-14 18:45 ` Thomas Huth
2017-11-14 18:46 ` Max Reitz
2017-11-14 20:30 ` John Snow [this message]
2017-11-14 20:35 ` Max Reitz
2017-11-14 20:38 ` John Snow
2017-11-14 20:44 ` Max Reitz
2017-11-13 17:55 ` Eric Blake
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=e76811c5-6a5a-cf5e-2571-9e112e609740@redhat.com \
--to=jsnow@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).