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 v2 0/9] meson: Move the creation of the library to the main meson.build
Date: Tue, 6 Oct 2020 15:09:52 +0200 [thread overview]
Message-ID: <8181d403-ab64-5af0-4916-9789d87a6b2c@redhat.com> (raw)
In-Reply-To: <20201006125602.2311423-1-philmd@redhat.com>
On 06/10/20 14:55, Philippe Mathieu-Daudé wrote:
> Make Meson machinery more consistent, as requested by Paolo.
>
> Since v1: addressed Paolo's review comments
> - Drop migration RFC patch
> - Move comment block
>
> Series coded while listening to Brass Against songs:
>
> https://www.youtube.com/channel/UClJMqrWQJ8OYWJ4ZdfqZdeQ
>
> and available in the Git repository at:
>
> https://gitlab.com/philmd/qemu.git branches/meson_libraries_consistency
>
> Philippe Mathieu-Daudé (9):
> 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(-)
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-10-06 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 12:55 [PATCH v2 0/9] meson: Move the creation of the library to the main meson.build Philippe Mathieu-Daudé
2020-10-06 12:55 ` [PATCH v2 1/9] meson.build: Add comments to clarify code organization Philippe Mathieu-Daudé
2020-10-06 12:55 ` [PATCH v2 2/9] meson.build: Sort sourcesets alphabetically Philippe Mathieu-Daudé
2020-10-06 12:55 ` [PATCH v2 3/9] hw/core: Move the creation of the library to the main meson.build Philippe Mathieu-Daudé
2020-10-06 12:55 ` [PATCH v2 4/9] chardev: " Philippe Mathieu-Daudé
2020-10-06 12:55 ` [PATCH v2 5/9] migration: " Philippe Mathieu-Daudé
2020-10-06 12:55 ` [PATCH v2 6/9] io: " Philippe Mathieu-Daudé
2020-10-06 12:56 ` [PATCH v2 7/9] crypto: " Philippe Mathieu-Daudé
2020-10-06 12:56 ` [PATCH v2 8/9] authz: " Philippe Mathieu-Daudé
2020-10-06 12:56 ` [PATCH v2 9/9] qom: " Philippe Mathieu-Daudé
2020-10-06 13:00 ` [PATCH v2 0/9] meson: " no-reply
2020-10-06 13:04 ` Philippe Mathieu-Daudé
2020-10-06 13:09 ` Paolo Bonzini [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=8181d403-ab64-5af0-4916-9789d87a6b2c@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).