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 v6 (for 2.10) 1/1] docs: document deprecation policy & deprecated features in appendix
Date: Tue, 25 Jul 2017 13:58:27 +0200 [thread overview]
Message-ID: <f5a11d2c-34ce-9bf6-0ad5-8cded201192c@redhat.com> (raw)
In-Reply-To: <20170725113638.7019-1-berrange@redhat.com>
On 25.07.2017 13:36, Daniel P. Berrange wrote:
> The deprecation of features in QEMU is totally adhoc currently,
s/adhoc/ad hoc/
> 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 | 175 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 175 insertions(+)
[...]
> +@subsection -net vlan (since 2.9.0)
> +
> +The ``-net van=NN'' argument is partially replaced with the
s/van/vlan/
Apart from the nits, looks fine to me now:
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2017-07-25 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 11:26 [Qemu-devel] [PATCH v6 (for 2.10) 0/1] Document deprecation policy & features Daniel P. Berrange
2017-07-25 11:36 ` [Qemu-devel] [PATCH v6 (for 2.10) 1/1] docs: document deprecation policy & deprecated features in appendix Daniel P. Berrange
2017-07-25 11:58 ` Thomas Huth [this message]
2017-07-25 12:49 ` [Qemu-devel] [PATCH v6 (for 2.10) 0/1] Document deprecation policy & features Stefan Hajnoczi
2017-07-25 13:30 ` Paolo Bonzini
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=f5a11d2c-34ce-9bf6-0ad5-8cded201192c@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).