From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Cleber Rosa" <crosa@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Deprecate Python 2 support
Date: Tue, 7 May 2019 10:44:54 +0100 [thread overview]
Message-ID: <20190507094454.GI27205@redhat.com> (raw)
In-Reply-To: <20190503193721.18459-1-ehabkost@redhat.com>
On Fri, May 03, 2019 at 04:37:21PM -0300, Eduardo Habkost wrote:
> Python 2 will reach end of life in January 1 2020. Declare it as
> deprecated.
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> configure | 8 ++++++++
> qemu-deprecated.texi | 8 ++++++++
> 2 files changed, 16 insertions(+)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
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:[~2019-05-07 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 19:37 [Qemu-devel] [PATCH] Deprecate Python 2 support Eduardo Habkost
2019-05-03 19:37 ` Eduardo Habkost
2019-05-04 6:27 ` Thomas Huth
2019-05-04 6:27 ` Thomas Huth
2019-05-06 14:12 ` Markus Armbruster
2019-05-07 0:53 ` Eduardo Habkost
2019-05-07 9:44 ` Daniel P. Berrangé [this message]
2019-05-07 10:38 ` Kevin Wolf
2019-05-07 10:47 ` Daniel P. Berrangé
2019-05-08 12:50 ` Markus Armbruster
2019-05-08 17:57 ` Eduardo Habkost
2019-06-06 22:28 ` 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=20190507094454.GI27205@redhat.com \
--to=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--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).