From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Juan Quintela" <quintela@redhat.com>
Subject: Re: [PATCH 00/10] meson: Move the creation of the library to the main meson.build
Date: Tue, 6 Oct 2020 13:29:57 +0200 [thread overview]
Message-ID: <c3fe9454-dd67-62c5-d3dd-8852810e7969@redhat.com> (raw)
In-Reply-To: <20201006111219.2300921-1-philmd@redhat.com>
On 06/10/20 13:12, Philippe Mathieu-Daudé wrote:
> Make Meson machinery more consistent, as requested by Paolo.
>
> Philippe Mathieu-Daudé (10):
> migration: Only add migration files to the Meson sourceset
> meson.build: Add comments to clarify code organization
> meson.build: Sort sourcesets alphabetically
> hw/core: Move the creation of the library to the main meson.build
> chardev: Move the creation of the library to the main meson.build
> migration: Move the creation of the library to the main meson.build
> io: Move the creation of the library to the main meson.build
> crypto: Move the creation of the library to the main meson.build
> authz: Move the creation of the library to the main meson.build
> qom: Move the creation of the library to the main meson.build
>
> meson.build | 86 ++++++++++++++++++++++++++++++++++++++-----
> authz/meson.build | 10 -----
> chardev/meson.build | 6 ---
> crypto/meson.build | 10 -----
> hw/core/meson.build | 6 ---
> io/meson.build | 10 -----
> migration/meson.build | 8 +---
> qom/meson.build | 8 ----
> 8 files changed, 77 insertions(+), 67 deletions(-)
>
Nice! Apart from the change to patch 1, perhaps move the "Targets"
headline a little earlier, namely just before
foreach m : block_mods + softmmu_mods
...
endforeach
Thanks!
Paolo
next prev parent reply other threads:[~2020-10-06 11:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 11:12 [PATCH 00/10] meson: Move the creation of the library to the main meson.build Philippe Mathieu-Daudé
2020-10-06 11:12 ` [RFC PATCH 01/10] migration: Only add migration files to the Meson sourceset Philippe Mathieu-Daudé
2020-10-06 11:13 ` Philippe Mathieu-Daudé
2020-10-06 11:25 ` Paolo Bonzini
2020-10-06 11:12 ` [PATCH 02/10] meson.build: Add comments to clarify code organization Philippe Mathieu-Daudé
2020-10-06 11:24 ` Paolo Bonzini
2020-10-06 11:12 ` [PATCH 03/10] meson.build: Sort sourcesets alphabetically Philippe Mathieu-Daudé
2020-10-06 11:12 ` [PATCH 04/10] hw/core: Move the creation of the library to the main meson.build Philippe Mathieu-Daudé
2020-10-06 11:12 ` [PATCH 05/10] chardev: " Philippe Mathieu-Daudé
2020-10-06 11:12 ` [PATCH 06/10] migration: " Philippe Mathieu-Daudé
2020-10-06 11:25 ` Paolo Bonzini
2020-10-06 11:29 ` Philippe Mathieu-Daudé
2020-10-06 11:12 ` [PATCH 07/10] io: " Philippe Mathieu-Daudé
2020-10-06 11:12 ` [PATCH 08/10] crypto: " Philippe Mathieu-Daudé
2020-10-06 11:12 ` [PATCH 09/10] authz: " Philippe Mathieu-Daudé
2020-10-06 11:12 ` [PATCH 10/10] qom: " Philippe Mathieu-Daudé
2020-10-06 11:29 ` Paolo Bonzini [this message]
2020-10-06 12:48 ` [PATCH 00/10] meson: " 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=c3fe9454-dd67-62c5-d3dd-8852810e7969@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).