qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: Re: [PULL v7 000/151] Meson-based build system
Date: Wed, 19 Aug 2020 16:59:21 -0500	[thread overview]
Message-ID: <3689e853-b267-a553-a78f-d906618512db@redhat.com> (raw)
In-Reply-To: <20200819213203.17876-1-pbonzini@redhat.com>

On 8/19/20 4:32 PM, Paolo Bonzini wrote:
> The following changes since commit d0ed6a69d399ae193959225cdeaa9382746c91cc:
> 
>    Update version for v5.1.0 release (2020-08-11 17:07:03 +0100)
> 
> are available in the Git repository at:
> 
>    https://gitlab.com/bonzini/qemu.git tags/for-upstream

Unrelated to the pull request proper, but I note in MAINTAINERS that you 
have listed:

T: git https://github.com/bonzini/qemu.git scsi-next

Have you switched to gitlab as your personal mirroring preference, and 
if so, should MAINTAINERS be updated?

> 
> for you to fetch changes up to 2eddb3c65821dce76433d5da6f3e6419349d1b77:
> 
>    docs: convert build system documentation to rST (2020-08-19 16:13:30 -0400)
> 
> v6->v7:
> * new patch to preserve compatibility symlinks from previous binary locations
> * fixed cut-and-paste error in linux-user/mips/meson.build
> * preserve compatibility check-block target even if no block tests are defined

FWIW: I haven't done any review or testing of the earlier iterations of 
this series.  But since it will be landing soon, I merged this tag to an 
incremental build tree that was previously sitting on a finished 5.1 
build (sources in qemu/, VPATH build in qemu/build/), typed 'make' then 
'make check', and everything finished successfully at least for my 
typical setup.  So good job on getting this massive rewrite in while 
still preserving at least the common 'make' interface.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org



  reply	other threads:[~2020-08-19 22:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 21:32 [PULL v7 000/151] Meson-based build system Paolo Bonzini
2020-08-19 21:59 ` Eric Blake [this message]
2020-08-19 22:08   ` Paolo Bonzini
2020-08-20 10:33 ` Peter Maydell
2020-08-20 11:52   ` Paolo Bonzini
2020-08-20 14:54     ` Peter Maydell
2020-08-20 16:02       ` Paolo Bonzini
2020-08-20 16:10         ` Peter Maydell
2020-08-21  6:15 ` Howard Spoelstra
2020-08-21 10:58   ` Howard Spoelstra
2020-08-21 12:33     ` Paolo Bonzini
2020-08-21 16:11       ` Howard Spoelstra
2020-08-21 16:16         ` Paolo Bonzini
2020-08-24 16:18       ` Daniel P. Berrangé

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=3689e853-b267-a553-a78f-d906618512db@redhat.com \
    --to=eblake@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).