From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL v3 00/68] i386, build system, KVM changes for 2023-05-18
Date: Mon, 22 May 2023 10:27:32 +0200 [thread overview]
Message-ID: <87o7mcojnv.fsf@pond.sub.org> (raw)
In-Reply-To: <20230518114025.1006732-1-pbonzini@redhat.com> (Paolo Bonzini's message of "Thu, 18 May 2023 13:40:24 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> The following changes since commit d27e7c359330ba7020bdbed7ed2316cb4cf6ffc1:
>
> qapi/parser: Drop two bad type hints for now (2023-05-17 10:18:33 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/bonzini/qemu.git tags/for-upstream
>
> for you to fetch changes up to fe3ab4eb2de46076cbafcbc86b22e71ad24894c6:
>
> docs/devel: update build system docs (2023-05-18 13:35:28 +0200)
>
> ----------------------------------------------------------------
> * kvm: enable dirty ring for arm64
> * target/i386: new features
> * target/i386: AVX fixes
> * configure: create a python venv unconditionally
> * meson: bump to 0.63.0 and move tests from configure
> * meson: Pass -j option to sphinx
> * drop support for Python 3.6
Halleluja! Thank you both.
> * fix check-python-tox
> * fix "make clean" in the source directory
prev parent reply other threads:[~2023-05-22 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 11:40 [PULL v3 00/68] i386, build system, KVM changes for 2023-05-18 Paolo Bonzini
2023-05-18 11:40 ` [PULL 59/68] build: move warning flag selection to meson Paolo Bonzini
2023-05-18 16:28 ` [PULL v3 00/68] i386, build system, KVM changes for 2023-05-18 Richard Henderson
2023-05-19 14:39 ` Peter Maydell
2023-05-19 16:51 ` Paolo Bonzini
2023-05-19 17:01 ` Peter Maydell
2023-05-19 17:31 ` Paolo Bonzini
2023-05-19 17:45 ` Peter Maydell
2023-05-19 18:03 ` Paolo Bonzini
2023-05-22 8:27 ` Markus Armbruster [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=87o7mcojnv.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=jsnow@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.