From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Cleber Rosa" <crosa@redhat.com>
Subject: [Qemu-devel] [PULL 0/2] Python 3 compatibility fixes
Date: Fri, 25 Jan 2019 12:06:08 -0200 [thread overview]
Message-ID: <20190125140610.7810-1-ehabkost@redhat.com> (raw)
The following changes since commit 9dd0d8111fbb8015db75a38933aee1d45f9e64a3:
Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2019-01-24' into staging (2019-01-25 11:52:12 +0000)
are available in the Git repository at:
git://github.com/ehabkost/qemu.git tags/python-next-pull-request
for you to fetch changes up to 651514df88fd53d537b3b78a7548663cc0816b1b:
decodetree: re.fullmatch was added in 3.4 (2019-01-25 11:41:42 -0200)
----------------------------------------------------------------
Python 3 compatibility fixes
----------------------------------------------------------------
Nisarg Shah (1):
device-crash-test: Python 3 compatibility fix
Paolo Bonzini (1):
decodetree: re.fullmatch was added in 3.4
scripts/decodetree.py | 2 +-
scripts/device-crash-test | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.18.0.rc1.1.g3f1ff2140
next reply other threads:[~2019-01-25 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 14:06 Eduardo Habkost [this message]
2019-01-25 14:06 ` [Qemu-devel] [PULL 1/2] device-crash-test: Python 3 compatibility fix Eduardo Habkost
2019-01-25 14:06 ` [Qemu-devel] [PULL 2/2] decodetree: re.fullmatch was added in 3.4 Eduardo Habkost
2019-01-25 18:43 ` [Qemu-devel] [PULL 0/2] Python 3 compatibility fixes Peter Maydell
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=20190125140610.7810-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).