From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH v4 0/2] vl: Deprecate auto-loading of qemu.conf
Date: Tue, 3 Oct 2017 23:50:41 -0300 [thread overview]
Message-ID: <20171004025043.3788-1-ehabkost@redhat.com> (raw)
This missed v2.9 and v2.10. Let's try again: we can include this
on v2.11, and remove the default config file in QEMU 2.13 or
2.14.
Changes v3 -> v4:
* Use warn_report() instead of error_report("warning: ...")
(Eric Blake)
* Document as a deprecated feature in qemu-doc.texi
* Updated Subject line
(was "vl: Print warning if a non-empty default config file is found")
Changes v2 -> v3:
* Rebase to latest qemu.git master
Changes v1 -> v2:
* Remove unnecessary translation of qemu_config_parse()
erros to -EINVAL at block/blkdebug.c:read_config()
* Suggsted-by: Markus Armbruster <armbru@redhat.com>
We plan to remove support for /etc/qemu/qemu.conf in the near
future. Make QEMU print a warning in case there a non-empty
/etc/qemu/qemu.conf is loaded, so users have time to adapt.
Eduardo Habkost (2):
config: qemu_config_parse() return number of config groups
vl: Deprecate auto-loading of qemu.conf
block/blkdebug.c | 1 -
util/qemu-config.c | 15 +++++++--------
vl.c | 6 ++++++
qemu-doc.texi | 8 ++++++++
4 files changed, 21 insertions(+), 9 deletions(-)
--
2.13.5
next reply other threads:[~2017-10-04 2:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 2:50 Eduardo Habkost [this message]
2017-10-04 2:50 ` [Qemu-devel] [PATCH v4 1/2] config: qemu_config_parse() return number of config groups Eduardo Habkost
2017-10-04 20:41 ` Eduardo Habkost
2017-10-04 2:50 ` [Qemu-devel] [PATCH v4 2/2] vl: Deprecate auto-loading of qemu.conf Eduardo Habkost
2017-10-04 5:42 ` Markus Armbruster
2017-10-04 12:23 ` Eduardo Habkost
2017-10-04 20:57 ` Eduardo Habkost
2017-10-05 5:00 ` Markus Armbruster
2017-10-05 12:34 ` Eduardo Habkost
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=20171004025043.3788-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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.