From: Richard Henderson <richard.henderson@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PULL 0/7] Python fixes and related patches
Date: Mon, 22 May 2023 07:02:20 -0700 [thread overview]
Message-ID: <6be5313c-db9c-4fea-5b32-c0231977d2f8@linaro.org> (raw)
In-Reply-To: <20230520190632.7491-1-pbonzini@redhat.com>
On 5/20/23 12:06, Paolo Bonzini wrote:
> The following changes since commit f0b95ab6b8192d84338496a0b6fd8f2c08a4a3a8:
>
> Merge tag 'for-upstream' ofhttps://gitlab.com/bonzini/qemu into staging (2023-05-18 07:52:12 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/bonzini/qemu.git tags/for-upstream-urgent
>
> for you to fetch changes up to 4b424c757188f7a47630a4d8edcf4ad9f19255bc:
>
> scripts: make sure scripts are invoked via $(PYTHON) (2023-05-19 20:40:29 +0200)
>
> ----------------------------------------------------------------
> Fixes for Python venv changes
Applied, thanks. Please update https://wiki.qemu.org/ChangeLog/8.1 as appropriate.
r~
prev parent reply other threads:[~2023-05-22 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 19:06 [PULL 0/7] Python fixes and related patches Paolo Bonzini
2023-05-20 19:06 ` [PULL 1/7] remove remaining traces of meson submodule Paolo Bonzini
2023-05-20 19:06 ` [PULL 2/7] mkvenv: replace distlib.database with importlib.metadata/pkg_resources Paolo Bonzini
2023-05-20 19:06 ` [PULL 3/7] build: rebuild build.ninja using "meson setup --reconfigure" Paolo Bonzini
2023-05-20 19:06 ` [PULL 4/7] configure: fix backwards-compatibility for meson sphinx_build option Paolo Bonzini
2023-05-20 19:06 ` [PULL 5/7] mkvenv: pass first missing package to diagnose() Paolo Bonzini
2023-05-20 19:06 ` [PULL 6/7] gitlab: custom-runners: preserve more artifacts for debugging Paolo Bonzini
2023-05-20 19:06 ` [PULL 7/7] scripts: make sure scripts are invoked via $(PYTHON) Paolo Bonzini
2023-05-22 14:02 ` Richard Henderson [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=6be5313c-db9c-4fea-5b32-c0231977d2f8@linaro.org \
--to=richard.henderson@linaro.org \
--cc=pbonzini@redhat.com \
--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).