All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] Document deprecated features & support lifecycle
Date: Tue, 4 Jul 2017 13:27:38 +0100	[thread overview]
Message-ID: <20170704122738.GM3135@redhat.com> (raw)
In-Reply-To: <f22d82b6-cd4b-b71c-179e-2f590ddb19b8@redhat.com>

On Tue, Jul 04, 2017 at 02:21:28PM +0200, Thomas Huth wrote:
> On 04.07.2017 13:14, Daniel P. Berrange wrote:
> [...]
> >  - Not listing the '-6' and '-e' args to qemu-img create. Those
> >    were never deprecations, because the functionality was
> >    immediately turned into a fatal error.
> How did you come to that conclusion? As far as I can see, the -6 option
> has been added by commit ec36ba14748e140dda2 and that was part of QEMU
> v0.10. The deprecation was done in commit eec77d9e712bd415 and that was
> part of QEMU v0.14.

A 'deprecation' message implies that the functionality continues to
work, but the user gets a warning that its going away. In this case
the user gets a warning, and the functionality is unusable - qemu-img
just exits immediately. This isn't deprecation in any normal sense,
it is just immediate feature removal with an message telling you it
has already been deleted :-(

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2017-07-04 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 11:14 [Qemu-devel] [PATCH v3 0/2] Document deprecated features & support lifecycle Daniel P. Berrange
2017-07-04 11:14 ` [Qemu-devel] [PATCH v3 1/2] docs: document support lifetime for features Daniel P. Berrange
2017-07-04 12:43   ` Thomas Huth
2017-07-04 13:52     ` Daniel P. Berrange
2017-07-04 11:14 ` [Qemu-devel] [PATCH v3 2/2] docs: document deprecated features in appendix Daniel P. Berrange
2017-07-04 12:59   ` Thomas Huth
2017-07-04 13:53     ` Daniel P. Berrange
2017-07-04 12:00 ` [Qemu-devel] [PATCH v3 0/2] Document deprecated features & support lifecycle Peter Maydell
2017-07-04 12:16   ` Daniel P. Berrange
2017-07-04 13:03     ` Thomas Huth
2017-07-04 12:21 ` Thomas Huth
2017-07-04 12:27   ` Daniel P. Berrange [this message]
2017-07-04 12:34     ` Thomas Huth

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=20170704122738.GM3135@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --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 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.