From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, Eric Blake <eblake@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] configure: Require Python 2.6
Date: Thu, 1 Oct 2015 13:06:33 +0200 [thread overview]
Message-ID: <560D13B9.8060806@redhat.com> (raw)
In-Reply-To: <CAFEAcA_dr0HwDqbL=8x=7ijoxvH0JBrer1QCTocFkRS1qZny_w@mail.gmail.com>
On 30/09/2015 00:25, Peter Maydell wrote:
> On 29 September 2015 at 22:35, Eric Blake <eblake@redhat.com> wrote:
>> ping
>>
>> On 09/04/2015 04:44 PM, Peter Maydell wrote:
>>> On 4 September 2015 at 20:53, Markus Armbruster <armbru@redhat.com> wrote:
>>>> RHEL-6 and SLES-11 provide Python 2.6. It'll also work on OS X back
>>>> to 10.6.
>>>>
>>>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>>>
>>> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>>>
>>> I wonder if we're ever going to need to add that Python 3
>>> support the error message alludes to :-)
>>
>> Which tree will this be going through?
>
> Random buildsystem stuff usually gets picked up by Paolo.
I've queued it but I'm a bit busy, so I'm not going to send the next
pull request until I've managed to test the record-replay stuff. Anyone
can feel free to pick up this patch or others.
Paolo
next prev parent reply other threads:[~2015-10-01 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 19:53 [Qemu-devel] [PATCH] configure: Require Python 2.6 Markus Armbruster
2015-09-04 22:44 ` Peter Maydell
2015-09-07 8:49 ` Daniel P. Berrange
2015-09-09 17:39 ` Steve Ellcey
2015-09-09 17:43 ` Peter Maydell
2015-09-29 21:35 ` Eric Blake
2015-09-29 22:25 ` Peter Maydell
2015-10-01 11:06 ` Paolo Bonzini [this message]
2015-10-01 5:32 ` Markus Armbruster
2015-09-07 8:50 ` Daniel P. Berrange
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=560D13B9.8060806@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@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).