From: "Daniel P. Berrange" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Vincent Palatin <vpalatin@chromium.org>
Subject: Re: [Qemu-devel] [PATCH] Deprecate '-enable-kvm' and '-enable-hax' in favour of '-accel'
Date: Tue, 2 May 2017 11:21:05 +0100 [thread overview]
Message-ID: <20170502102105.GH3459@redhat.com> (raw)
In-Reply-To: <1493719600-30853-1-git-send-email-thuth@redhat.com>
On Tue, May 02, 2017 at 12:06:40PM +0200, Thomas Huth wrote:
> The '-enable-...' option do not make too much sense: They do not
> allow additional parameters, using '-accel xxx' is shorter than
> '-enable-xxx' and we're also inconsistent here, since there is
> no '-enable-xen' option available. So let's try to convince the
> users to use '-accel xxx' instead.
What is our general approach to deciding which of our "legacy" parameters
are merely syntactic sugar for other parameters, vs stuff we want to
deprecate & eventually remove ?
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-05-02 10:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 10:06 [Qemu-devel] [PATCH] Deprecate '-enable-kvm' and '-enable-hax' in favour of '-accel' Thomas Huth
2017-05-02 10:21 ` Daniel P. Berrange [this message]
2017-05-02 10:29 ` Thomas Huth
2017-05-02 10:32 ` Christian Borntraeger
2017-05-02 10:37 ` Thomas Huth
2017-05-02 10:48 ` Christian Borntraeger
2017-05-02 11:26 ` Thomas Huth
2017-05-02 11:59 ` Daniel P. Berrange
2017-05-02 12:07 ` Thomas Huth
2017-05-02 12:14 ` Thomas Huth
2017-05-02 12:16 ` Daniel P. Berrange
2017-05-02 12:38 ` Daniel P. Berrange
2017-05-02 12:46 ` Thomas Huth
2017-05-02 13:22 ` Paolo Bonzini
2017-05-02 15:01 ` Markus Armbruster
2017-05-02 15:09 ` Paolo Bonzini
2017-05-02 15:53 ` Thomas Huth
2017-05-02 16:08 ` Paolo Bonzini
2017-05-02 16:19 ` Thomas Huth
2017-05-02 16:22 ` Paolo Bonzini
2017-05-03 8:07 ` Markus Armbruster
2017-05-02 12:21 ` Christian Borntraeger
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=20170502102105.GH3459@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=vpalatin@chromium.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.