From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org
Subject: [PATCH 0/3] meson.build: Group some entries in separate summary sections
Date: Fri, 2 Jun 2023 19:18:29 +0200 [thread overview]
Message-ID: <20230602171832.533739-1-thuth@redhat.com> (raw)
For the average user, it is likely quite difficult which library is
responsible for different features that QEMU supports. Let's make
it a little bit easier for them and put some libraries into separate
groups in the summary output of meson.
Thomas Huth (3):
meson.build: Group the UI entries in a separate summary section
meson.build: Group the network backend entries in a separate summary
section
meson.build: Group the audio backend entries in a separate summary
section
meson.build | 48 +++++++++++++++++++++++++++++++-----------------
1 file changed, 31 insertions(+), 17 deletions(-)
--
2.31.1
next reply other threads:[~2023-06-02 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 17:18 Thomas Huth [this message]
2023-06-02 17:18 ` [PATCH 1/3] meson.build: Group the UI entries in a separate summary section Thomas Huth
2023-06-02 20:01 ` Philippe Mathieu-Daudé
2023-06-02 17:18 ` [PATCH 2/3] meson.build: Group the network backend " Thomas Huth
2023-06-02 20:03 ` Philippe Mathieu-Daudé
2023-06-05 6:08 ` Thomas Huth
2023-06-02 17:18 ` [PATCH 3/3] meson.build: Group the audio " Thomas Huth
2023-06-02 20:03 ` Philippe Mathieu-Daudé
2023-06-03 3:38 ` [PATCH 0/3] meson.build: Group some entries in separate summary sections Richard Henderson
2023-06-05 8:27 ` Paolo Bonzini
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=20230602171832.533739-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@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).