From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/2] Build bugfixes for QEMU 7.0, 2022-03-29
Date: Tue, 29 Mar 2022 19:52:46 +0000 [thread overview]
Message-ID: <CAFEAcA_uDoBzJWCQ+pfRmKogvvobL_8r_a7sCOrFt7Bc7f+dRg@mail.gmail.com> (raw)
In-Reply-To: <20220329140027.869953-1-pbonzini@redhat.com>
On Tue, 29 Mar 2022 at 15:03, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> The following changes since commit f345abe36527a8b575482bb5a0616f43952bf1f4:
>
> Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into staging (2022-03-25 10:14:47 +0000)
>
> are available in the Git repository at:
>
> https://gitlab.com/bonzini/qemu.git tags/for-upstream
>
> for you to fetch changes up to 36e38426ff40c9ba86d4e66027f3a98747890623:
>
> tests/tcg: really fix path to target configuration (2022-03-29 15:58:39 +0200)
>
> ----------------------------------------------------------------
> Build bugfixes.
>
> ----------------------------------------------------------------
> Paolo Bonzini (2):
> virtio: fix --enable-vhost-user build on non-Linux
> tests/tcg: really fix path to target configuration
That tag doesn't seem to have these contents (it still has the
patches you sent in your last pullreq last week). Forgot to push?
(Trying to re-merge an already merged tag confuses my merge
scripts, incidentally -- I should fix that...)
-- PMM
next prev parent reply other threads:[~2022-03-29 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 14:00 [PULL 0/2] Build bugfixes for QEMU 7.0, 2022-03-29 Paolo Bonzini
2022-03-29 14:00 ` [PULL 1/2] virtio: fix --enable-vhost-user build on non-Linux Paolo Bonzini
2022-03-29 14:00 ` [PULL 2/2] tests/tcg: really fix path to target configuration Paolo Bonzini
2022-03-29 19:52 ` Peter Maydell [this message]
2022-03-29 22:31 ` [PULL 0/2] Build bugfixes for QEMU 7.0, 2022-03-29 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=CAFEAcA_uDoBzJWCQ+pfRmKogvvobL_8r_a7sCOrFt7Bc7f+dRg@mail.gmail.com \
--to=peter.maydell@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).