From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Peter Maydell <peter.maydell@linaro.org>,
Alistair Francis <alistair.francis@xilinx.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Richard Henderson <rth@twiddle.net>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 5/6] hw/i386: deprecate the pc-0.10 and pc-0.11 machines
Date: Wed, 8 Nov 2017 11:43:05 +0100 [thread overview]
Message-ID: <c7dcbf77-92ac-78f5-a85e-0f1ba1003fc9@redhat.com> (raw)
In-Reply-To: <20171108091303.GH12670@redhat.com>
On 08.11.2017 10:13, Daniel P. Berrange wrote:
> On Wed, Nov 08, 2017 at 12:28:00AM -0300, Philippe Mathieu-Daudé wrote:
>> Hi Alexey,
>>
>> On 11/07/2017 11:48 PM, Alexey Kardashevskiy wrote:
>>> On 08/11/17 13:28, Philippe Mathieu-Daudé wrote:
>>>> Both are deprecated since 2.9.0
>>>
>>> May be so but I could not find where this happened in git history:
>>>
>>> [vpl1 qemu]$ git log -n1 --grep 'pc-0.10'
>>> f6d5a0bad2 2 years, 5 months ago Eduardo Habkost piix: Define PC_COMPAT_0_10
>>>
>>> Having some pointers in the commit log would be helpful imho, like [2/6].
>>
>> Ok! If there is positive feedback on this series I'll respin trying to
>> be more verbose.
>>
>> I took "2.9.0" from the wiki history [1], which is the formal way to go
>> as I understand:
>
> No, the wiki page content was just an initial jumping off point for
> discussions. The formal list of what's deprecated is kept in the
> qemu-doc.texi file in the "Deprecated features" appendix.
>
> We really ought to remove most of the content from that wiki page
> and just point to the formal docs, to avoid continued confusion
> like this.
I've changed the wording on the wiki page and added a pointer to the
qemu-doc there, so it's hopefully now clearer that the qemu-doc is the
mandatory list of deprecated features / interfaces.
Thomas
next prev parent reply other threads:[~2017-11-08 10:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 2:28 [Qemu-devel] [RFC PATCH 0/6] generic way to deprecate machines Philippe Mathieu-Daudé
2017-11-08 2:28 ` [Qemu-devel] [RFC PATCH 1/6] machine: add a deprecated_reason property Philippe Mathieu-Daudé
2017-11-08 10:23 ` Thomas Huth
2017-11-08 10:27 ` Daniel P. Berrange
2017-11-08 20:29 ` Eduardo Habkost
2018-01-22 2:10 ` Philippe Mathieu-Daudé
2018-01-22 6:21 ` Thomas Huth
2017-11-08 2:28 ` [Qemu-devel] [RFC PATCH 2/6] hw/arm: deprecate the EP108 board Philippe Mathieu-Daudé
2017-11-08 9:17 ` Daniel P. Berrange
2017-11-08 2:28 ` [Qemu-devel] [RFC PATCH 3/6] hw/arm: deprecate the Gumstix boards Philippe Mathieu-Daudé
2017-11-08 2:28 ` [Qemu-devel] [RFC PATCH 4/6] hw/ppc: deprecate the PReP machine Philippe Mathieu-Daudé
2017-11-08 2:28 ` [Qemu-devel] [RFC PATCH 5/6] hw/i386: deprecate the pc-0.10 and pc-0.11 machines Philippe Mathieu-Daudé
2017-11-08 2:48 ` Alexey Kardashevskiy
2017-11-08 3:28 ` Philippe Mathieu-Daudé
2017-11-08 9:13 ` Daniel P. Berrange
2017-11-08 10:43 ` Thomas Huth [this message]
2017-11-08 9:16 ` Daniel P. Berrange
2017-11-08 10:15 ` Thomas Huth
2017-11-08 11:36 ` Thomas Huth
2017-11-08 2:28 ` [Qemu-devel] [RFC PATCH 6/6] hw/i386: deprecate the "isapc" machine Philippe Mathieu-Daudé
2017-11-08 3:29 ` Philippe Mathieu-Daudé
2017-11-08 9:09 ` Daniel P. Berrange
2017-11-08 9:44 ` Gerd Hoffmann
2017-11-08 10:05 ` Thomas Huth
2017-11-08 9:10 ` [Qemu-devel] [RFC PATCH 0/6] generic way to deprecate machines Daniel P. Berrange
2018-05-04 17:15 ` Thomas Huth
2018-05-08 15:47 ` Philippe Mathieu-Daudé
2018-05-11 13:55 ` [Qemu-devel] Publishing binary images for testing (was Re: [RFC PATCH 0/6] generic way to deprecate machines) Eduardo Habkost
2018-05-11 14:27 ` Cleber Rosa
2018-05-18 18:16 ` Alistair Francis
2018-05-22 16:17 ` Cleber Rosa
2018-05-22 16:34 ` Alistair Francis
2019-06-17 5:17 ` [Qemu-devel] Publishing binary images for testing Philippe Mathieu-Daudé
2019-08-16 10:51 ` Philippe Mathieu-Daudé
2019-08-19 13:10 ` Cleber Rosa
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=c7dcbf77-92ac-78f5-a85e-0f1ba1003fc9@redhat.com \
--to=thuth@redhat.com \
--cc=aik@ozlabs.ru \
--cc=alistair.francis@xilinx.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).