All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	qemu-block@nongnu.org
Subject: Insufficiently documented deprecated command arguments
Date: Wed, 11 Dec 2019 09:12:41 +0100	[thread overview]
Message-ID: <87tv67wa9y.fsf@dusky.pond.sub.org> (raw)

I went through the QAPI schema looking for deprecated stuff not
mentioned in qemu-deprecated.texi.  Here's what I found:

    Commit b33945cfff "block: Accept device model name for
    blockdev-open/close-tray" (v2.8.0) deprecated blockdev-open-tray,
    blockdev-close-tray argument @device.

    Commit 70e2cb3bd7 "block: Accept device model name for
    blockdev-change-medium" (v2.8.0) deprecated blockdev-change-medium
    argument @device.

    Commit 7a9877a026 "block: Accept device model name for
    block_set_io_throttle" (v2.8.0) deprecated block_set_io_throttle
    argument @device.

    Commit c01c214b69 "block: remove all encryption handling APIs"
    (v2.10.0) deprecated query-named-block-nodes result field
    encryption_key_missing and query-block result field
    inserted.encryption_key_missing.

    Commit c42e8742f5 "block: Use JSON null instead of "" to disable
    backing file" (v2.10.0) deprecated blockdev-add empty string
    argument @backing.

    These were missed in commit eb22aeca65 "docs: document deprecation
    policy & deprecated features in appendix" (v2.10.0).

    Commit 3c605f4074 "commit: Add top-node/base-node options" (v3.1.0)
    deprecated block-commit arguments @base and @top.

I can update qemu-deprecated.texi for these.

Now my question: I wonder whether we want to remove any of them right
away.



             reply	other threads:[~2019-12-11  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11  8:12 Markus Armbruster [this message]
2019-12-11  9:33 ` Insufficiently documented deprecated command arguments Peter Krempa
2019-12-11 10:14   ` Kevin Wolf
2019-12-11 10:51     ` Peter Krempa
2019-12-11 12:24       ` Kevin Wolf
2019-12-11 12:32         ` Daniel P. Berrangé
2019-12-11 12:55           ` Peter Krempa
2019-12-11 16:30             ` Markus Armbruster

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=87tv67wa9y.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@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.