From: Laszlo Ersek <lersek@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Gabriel L . Somlo" <somlo@cmu.edu>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] fw_cfg: RQFN rules, documentation
Date: Tue, 5 Apr 2016 11:20:46 +0200 [thread overview]
Message-ID: <5703836E.6070302@redhat.com> (raw)
In-Reply-To: <20160405113207-mutt-send-email-mst@redhat.com>
On 04/05/16 10:35, Michael S. Tsirkin wrote:
> On Mon, Apr 04, 2016 at 07:14:48PM +0200, Laszlo Ersek wrote:
>> On 04/04/16 17:57, Michael S. Tsirkin wrote:
>>
>>>> ... My question is, do we need the "opt/" prefix at all (for the future,
>>>> i.e., the non-historical cases)?
>>>> Looking at the last discussion, I
>>>> believe we converged on:
>>>>
>>>> - QEMU devs (future filenames): org.qemu/...
>>>> - users: com.my_company/...
>>>> - QEMU fw devs (future names): org.tianocore.edk2.ovmf/...
>>>> org.seabios/...
>>>> - QEMU fw devs hacking: <root-prefix-to-strip>/...
>>>>
>>>> Did you find something unsafe about this (necessitating "opt/")?
>>>>
>>>
>>> The reason to use the opt/ prefix is to avoid warning
>>> with QEMU 2.4 and 2.5.
>>
>> Sorry, it's been a long day :), and I don't understand your answer. Can
>> you please spell it out for me? How are QEMU 2.4 and 2.5 related to this
>> discussion?
>>
>> Thanks!
>> Laszlo
>
> People would want to use the same command line for QEMU 2.4, 2.5 and
> 2.6. If you use a prefix without opt with 2.4/2.5 you get a warning,
> and if people get a warning from a valid command line, that's not nice, so
> we want a prefix that does not cause a warning for these versions.
Ah, understood. Thanks.
Laszlo
prev parent reply other threads:[~2016-04-05 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 10:51 [Qemu-devel] [PATCH] fw_cfg: RQFN rules, documentation Michael S. Tsirkin
2016-04-04 13:09 ` Laszlo Ersek
2016-04-04 15:57 ` Michael S. Tsirkin
2016-04-04 17:14 ` Laszlo Ersek
2016-04-05 8:35 ` Michael S. Tsirkin
2016-04-05 9:20 ` Laszlo Ersek [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=5703836E.6070302@redhat.com \
--to=lersek@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
/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).