qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 2/2 (for 2.10)] docs: document deprecated features in appendix
Date: Tue, 25 Jul 2017 11:35:53 +0200	[thread overview]
Message-ID: <c54bf8d4-571e-e4b5-0103-e23be3785139@redhat.com> (raw)
In-Reply-To: <20170719100802.14094-3-berrange@redhat.com>

On 19.07.2017 12:08, Daniel P. Berrange wrote:
> The deprecation of features in QEMU is totally adhoc currently,
> with no way for the user to get a list of what is deprecated
> in each release. This adds an appendix to the doc that records
> when each deprecation was made and provides text explaining
> what to use instead, if anything.
> 
> Since there has been no formal policy around removal of deprecated
> features in the past, any deprecations prior to 2.10.0 are to be
> treated as if they had been made at the 2.10.0 release. Thus the
> earliest that existing deprecations will be deleted is the start
> of the 2.12.0 cycle.
> 
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
>  qemu-doc.texi | 168 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 168 insertions(+)
[...]
> +@subsection -monitor default=on (since 2.4.0)
> +
> +The ``default'' option to the ``-monitor'' argument is
> +now ignored. When multiple monitors were enabled, it
> +indicated which monitor would receive log messages
> +from the various subsystems. This feature is no longer
> +required as messages are now only sent to the monitor
> +in response to explicitly monitor commands.

BTW, seems like it's the "-mon" option, not the "-monitor" option that
has this "default" parameter?

 Thomas

  parent reply	other threads:[~2017-07-25  9:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 10:08 [Qemu-devel] [PATCH v5 0/2 (for 2.10] Document deprecated features & support lifecycle Daniel P. Berrange
2017-07-19 10:08 ` [Qemu-devel] [PATCH v5 1/2 (for 2.10)] docs: document support lifetime for features Daniel P. Berrange
2017-07-19 11:56   ` Thomas Huth
2017-07-24 13:49     ` Paolo Bonzini
2017-07-24 14:11       ` Daniel P. Berrange
2017-07-24 14:26         ` Paolo Bonzini
2017-07-24 14:47           ` Daniel P. Berrange
2017-07-24 14:58             ` Paolo Bonzini
2017-07-19 10:08 ` [Qemu-devel] [PATCH v5 2/2 (for 2.10)] docs: document deprecated features in appendix Daniel P. Berrange
2017-07-19 11:51   ` Thomas Huth
2017-07-25  9:35   ` Thomas Huth [this message]
2017-07-25 11:21     ` Daniel P. Berrange
2017-07-24 13:45 ` [Qemu-devel] [PATCH v5 0/2 (for 2.10] Document deprecated features & support lifecycle Stefan Hajnoczi

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=c54bf8d4-571e-e4b5-0103-e23be3785139@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.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).