From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.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>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>, "John Snow" <jsnow@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>, "Stefan Weil" <sw@weilnetz.de>
Subject: Re: [PATCH v8 0/4] cutils: Introduce bundle mechanism
Date: Sat, 25 Jun 2022 00:31:11 +0900 [thread overview]
Message-ID: <75c27174-98fb-cd45-7aef-43ef40ee8775@gmail.com> (raw)
In-Reply-To: <cc7f1005-fe08-320e-0108-8585760de7b5@redhat.com>
On 2022/06/25 0:26, Paolo Bonzini wrote:
> The only change I'd make (which I can do when queueing the patch) is to
> change the directory name to something "strange" like "=install", so
> that it's unlikely to have a directory named like that in the $bindir.
>
> Any opinions?
Actually I prepended qemu- to the directory because all executables of
QEMU has the prefix. We can safely say QEMU installation will never
collide if no file prefixed with qemu- exists in the bindir.
If anyone has an idea what should follow "qemu-", please tell us.
Regards,
Akihiko Odaki
prev parent reply other threads:[~2022-06-24 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:50 [PATCH v8 0/4] cutils: Introduce bundle mechanism Akihiko Odaki
2022-06-24 14:50 ` [PATCH v8 1/4] tests/vm: do not specify -bios option Akihiko Odaki
2022-06-24 14:50 ` [PATCH v8 2/4] cutils: Introduce bundle mechanism Akihiko Odaki
2022-06-24 15:26 ` Thomas Huth
2022-06-24 14:50 ` [PATCH v8 3/4] datadir: Use " Akihiko Odaki
2022-06-24 14:50 ` [PATCH v8 4/4] module: " Akihiko Odaki
2022-06-24 15:26 ` [PATCH v8 0/4] cutils: Introduce " Paolo Bonzini
2022-06-24 15:31 ` Akihiko Odaki [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=75c27174-98fb-cd45-7aef-43ef40ee8775@gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=jasowang@redhat.com \
--cc=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.