qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Cleber Rosa <crosa@redhat.com>,
	Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/4] Python queue for 5.0 soft freeze
Date: Fri, 20 Mar 2020 17:19:37 +0100	[thread overview]
Message-ID: <72ee2882-94b5-4eb5-7178-f8af29ca317f@redhat.com> (raw)
In-Reply-To: <CAFEAcA8M4P3a-QGA9qjOTmpsAKGBcKDG2KRhOC1V=iLHK3mqkw@mail.gmail.com>

On 3/20/20 5:14 PM, Peter Maydell wrote:
> On Fri, 20 Mar 2020 at 16:11, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>
>> On 3/20/20 4:59 PM, Peter Maydell wrote:
>>> On Wed, 18 Mar 2020 at 01:12, Eduardo Habkost <ehabkost@redhat.com> wrote:
>>>>
>>>> The following changes since commit d649689a8ecb2e276cc20d3af6d416e3c299cb17:
>>>>
>>>>     Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2020-03-17 18:33:05 +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 f4abfc6cb037da951e7977a67171f361fc6d21d7:
>>>>
>>>>     MAINTAINERS: add simplebench (2020-03-17 21:09:26 -0400)
>>>>
>>>> ----------------------------------------------------------------
>>>> Python queue for 5.0 soft freeze
>>>>
>>>> * Add scripts/simplebench (Vladimir Sementsov-Ogievskiy)
>>>>
>>>
>>>
>>> Applied, thanks.
>>
>> I guess there was a mis understanding with Eduardo, he was going to
>> resend this pullrequest due to:
>>
>> ERROR: please use python3 interpreter
> 
> Ah, sorry. I'd read the replies to this thread as meaning that
> those things were OK to fix as followup patches rather than
> requiring a respin of the pull.

As you noticed, scripts/simplebench/bench_block_job.py is not run in our 
tests, so no need to hold the other pull requests, we'll fix later.

Thanks,

Phil.



      reply	other threads:[~2020-03-20 16:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  1:12 [PULL 0/4] Python queue for 5.0 soft freeze Eduardo Habkost
2020-03-18  1:12 ` [PULL 1/4] scripts/simplebench: add simplebench.py Eduardo Habkost
2020-03-18  1:12 ` [PULL 2/4] scripts/simplebench: add qemu/bench_block_job.py Eduardo Habkost
2020-03-18  1:12 ` [PULL 3/4] scripts/simplebench: add example usage of simplebench Eduardo Habkost
2020-03-18  1:12 ` [PULL 4/4] MAINTAINERS: add simplebench Eduardo Habkost
2020-03-18  4:12 ` [PULL 0/4] Python queue for 5.0 soft freeze no-reply
2020-03-18  7:59   ` Vladimir Sementsov-Ogievskiy
2020-03-18 16:12     ` Eduardo Habkost
2020-03-18 16:16       ` Aleksandar Markovic
2020-03-18 17:02 ` [PATCH 5/4] scripts/simplebench: fix python script ! headers Vladimir Sementsov-Ogievskiy
2020-03-18 22:31   ` Philippe Mathieu-Daudé
2020-03-20 15:59 ` [PULL 0/4] Python queue for 5.0 soft freeze Peter Maydell
2020-03-20 16:11   ` Philippe Mathieu-Daudé
2020-03-20 16:14     ` Peter Maydell
2020-03-20 16:19       ` Philippe Mathieu-Daudé [this message]

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=72ee2882-94b5-4eb5-7178-f8af29ca317f@redhat.com \
    --to=philmd@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.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).