From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL v5 00/46] Next round of Meson bugfixes and cleanups
Date: Tue, 8 Sep 2020 16:13:50 +0200 [thread overview]
Message-ID: <dbc559bd-8e4c-d4d3-6719-143cd8b7b8d7@redhat.com> (raw)
In-Reply-To: <CAFEAcA8JZhrxNgayLaCGqQiGLhybvXo7qrXDUpVmkrX5FmjV5A@mail.gmail.com>
On 9/8/20 3:26 PM, Peter Maydell wrote:
> On Tue, 8 Sep 2020 at 10:45, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> The following changes since commit e11bd71f89649da3cff439c030d2ccac0cc914e3:
>>
>> Merge remote-tracking branch 'remotes/huth-gitlab/tags/pull-request-2020-09-07' into staging (2020-09-07 16:51:00 +0100)
>>
>> are available in the Git repository at:
>>
>> https://gitlab.com/bonzini/qemu.git tags/for-upstream
>>
>> for you to fetch changes up to ef6a0d6e3927464de67f70cb13abbfe67361e0c9:
>>
>> docs: update build system documentation (2020-09-08 07:21:55 +0200)
>>
>> ----------------------------------------------------------------
>> meson related:
>> * convert unit tests
>> * bugfixes for mtest2make
>> * miscellaneous bugfixes
>> * dead code removal and configure cleanups
>> * oss-fuzz fixes
>> * msys fixes
>
>
> Applied, thanks.
Once rebased I got:
Makefile.include:144: warning: overriding recipe for target 'check-block'
Makefile.mtest:1339: warning: ignoring old recipe for target 'check-block'
config-host.mak is out-of-date, running configure
Nothing to worry about as Makefile.mtest is generated.
I wonder if it is possible to avoid such warnings though...
next prev parent reply other threads:[~2020-09-08 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 9:44 [PULL v5 00/46] Next round of Meson bugfixes and cleanups Paolo Bonzini
2020-09-08 13:26 ` Peter Maydell
2020-09-08 14:13 ` Philippe Mathieu-Daudé [this message]
2020-09-08 14:21 ` Paolo Bonzini
2020-09-12 16:19 ` Philippe Mathieu-Daudé
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=dbc559bd-8e4c-d4d3-6719-143cd8b7b8d7@redhat.com \
--to=philmd@redhat.com \
--cc=pbonzini@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).