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: Mon, 4 Apr 2016 19:14:48 +0200 [thread overview]
Message-ID: <5702A108.6010002@redhat.com> (raw)
In-Reply-To: <20160404155722.GA695@redhat.com>
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
next prev parent reply other threads:[~2016-04-04 17:14 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 [this message]
2016-04-05 8:35 ` Michael S. Tsirkin
2016-04-05 9:20 ` Laszlo Ersek
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=5702A108.6010002@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 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.