From: Paolo Bonzini <pbonzini@redhat.com>
To: Akihiko Odaki <akihiko.odaki@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Jason Wang" <jasowang@redhat.com>,
qemu-devel@nongnu.org, Programmingkid <programmingkidx@gmail.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v7 0/6] cutils: Introduce bundle mechanism
Date: Wed, 15 Jun 2022 21:28:35 +0200 [thread overview]
Message-ID: <ce778937-f051-14c2-65b4-0341850c21fa@redhat.com> (raw)
In-Reply-To: <20220615173345.32456-1-akihiko.odaki@gmail.com>
On 6/15/22 19:33, Akihiko Odaki wrote:
> Developers often run QEMU without installing. The bundle mechanism
> allows to look up files which should be present in installation even in
> such a situation.
>
> It is a general mechanism and can find any files located relative
> to the installation tree. The build tree must have a new directory,
> qemu-bundle, to represent what files the installation tree would
> have for reference by the executables.
>
> v7: Properly fix --firmwarepath (Daniel P. Berrangé)
Please give people a little time to review. I left more comments on v6.
Paolo
prev parent reply other threads:[~2022-06-15 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 17:33 [PATCH v7 0/6] cutils: Introduce bundle mechanism Akihiko Odaki
2022-06-15 17:33 ` [PATCH v7 1/6] qga: Relocate a path emitted in the help text Akihiko Odaki
2022-06-20 13:06 ` Konstantin Kostiuk
2022-06-20 13:11 ` Marc-André Lureau
2022-06-20 13:12 ` Marc-André Lureau
2022-06-15 17:33 ` [PATCH v7 2/6] Remove prefixes from path configuration macros Akihiko Odaki
2022-06-15 17:33 ` [PATCH v7 3/6] cutils: Introduce bundle mechanism Akihiko Odaki
2022-06-15 17:33 ` [PATCH v7 4/6] datadir: Use " Akihiko Odaki
2022-06-15 17:33 ` [PATCH v7 5/6] ui/icons: " Akihiko Odaki
2022-06-15 17:33 ` [PATCH v7 6/6] net: " Akihiko Odaki
2022-06-15 19:28 ` 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=ce778937-f051-14c2-65b4-0341850c21fa@redhat.com \
--to=pbonzini@redhat.com \
--cc=akihiko.odaki@gmail.com \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--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).