From: Thomas Huth <thuth@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: [PATCH] qemu-deprecated: Remove text about Python 2
Date: Thu, 9 Jan 2020 10:51:16 +0100 [thread overview]
Message-ID: <20200109095116.18201-1-thuth@redhat.com> (raw)
Python 2 support has been removed, so we should now also remove
the announcement text for the deprecation.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
qemu-deprecated.texi | 8 --------
1 file changed, 8 deletions(-)
diff --git a/qemu-deprecated.texi b/qemu-deprecated.texi
index 7033e531de..8b23e98474 100644
--- a/qemu-deprecated.texi
+++ b/qemu-deprecated.texi
@@ -341,14 +341,6 @@ they have no effect when used with @option{-n} to skip image creation.
Silently ignored options can be confusing, so this combination of
options will be made an error in future versions.
-@section Build system
-
-@subsection Python 2 support (since 4.1.0)
-
-In the future, QEMU will require Python 3 to be available at
-build time. Support for Python 2 in scripts shipped with QEMU
-is deprecated.
-
@section Backwards compatibility
@subsection Runnability guarantee of CPU models (since 4.1.0)
--
2.18.1
next reply other threads:[~2020-01-09 9:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 9:51 Thomas Huth [this message]
2020-01-09 12:49 ` [PATCH] qemu-deprecated: Remove text about Python 2 Aleksandar Markovic
2020-01-29 22:13 ` Philippe Mathieu-Daudé
2020-01-29 23:18 ` Aleksandar Markovic
2020-01-29 23:26 ` Philippe Mathieu-Daudé
2020-01-13 22:36 ` John Snow
2020-01-14 10:08 ` Thomas Huth
2020-01-14 10:20 ` Daniel P. Berrangé
2020-01-14 15:53 ` John Snow
2020-01-15 16:04 ` Markus Armbruster
2020-01-15 17:16 ` John Snow
2020-01-30 22:09 ` Philippe Mathieu-Daudé
2020-03-16 18:16 ` John Snow
2020-01-30 22:13 ` Philippe Mathieu-Daudé
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=20200109095116.18201-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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).