From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Michal Privoznik" <mprivozn@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/1] Export machine type deprecation info through QMP
Date: Mon, 24 Jun 2019 19:48:06 -0300 [thread overview]
Message-ID: <b55a1b4d-7aa4-ccb4-33f8-aae583776d3d@redhat.com> (raw)
In-Reply-To: <20190624180326.GJ1862@habkost.net>
On 06/24/2019 03:03 PM, Eduardo Habkost wrote:
> Any objections to this? I'm planning to merge it this week.
IMHO, 1+. So I don't have objections.
- Wainer
>
> On Sat, Jun 08, 2019 at 08:34:46PM -0300, Eduardo Habkost wrote:
>> Changes v1 -> v2:
>> * I've decided to get rid of the status-message and
>> suggested-alternative fields, to avoid more bikeshedding.
>>
>> This series adds machine type deprecation information to the
>> output of the `query-machines` QMP command. With this, libvirt
>> and management software will be able to show this information to
>> users and/or suggest changes to VM configuration to avoid
>> deprecated machine types.
>>
>> Eduardo Habkost (1):
>> qmp: Add deprecation information to query-machines
>>
>> qapi/misc.json | 7 ++++++-
>> vl.c | 1 +
>> 2 files changed, 7 insertions(+), 1 deletion(-)
>>
>> --
>> 2.18.0.rc1.1.g3f1ff2140
>>
next prev parent reply other threads:[~2019-06-24 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 23:34 [Qemu-devel] [PATCH v2 0/1] Export machine type deprecation info through QMP Eduardo Habkost
2019-06-08 23:34 ` [Qemu-devel] [PATCH v2 1/1] qmp: Add deprecation information to query-machines Eduardo Habkost
2019-06-25 8:37 ` Marcel Apfelbaum
2019-06-24 18:03 ` [Qemu-devel] [PATCH v2 0/1] Export machine type deprecation info through QMP Eduardo Habkost
2019-06-24 22:48 ` Wainer dos Santos Moschetta [this message]
2019-06-25 12:00 ` 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=b55a1b4d-7aa4-ccb4-33f8-aae583776d3d@redhat.com \
--to=wainersm@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).