From: "Laszlo Ersek" <lersek@redhat.com>
To: Rebecca Cran <rebecca@bsdio.com>, devel@edk2.groups.io
Cc: michael.d.kinney@intel.com,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Peter Grehan <grehan@freebsd.org>
Subject: Re: [edk2-devel] Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg?
Date: Fri, 15 May 2020 11:42:12 +0200 [thread overview]
Message-ID: <56efcbf5-2fe8-4620-a98c-7b2bb60f0ceb@redhat.com> (raw)
In-Reply-To: <32735AC0-2354-4ADB-A4D5-A3D93DA00385@bsdio.com>
On 05/14/20 18:20, Rebecca Cran wrote:
>
>> On May 14, 2020, at 4:24 AM, Laszlo Ersek <lersek@redhat.com> wrote:
>>
>> - The community not having any human resources permanently dedicated to
>> bhyve regressions (testing, review, and post factum fixing) is fine, as
>> long as the bhyve stakeholders can live with a matching frequency of
>> regressions.
>
> Yes, I believe that would be acceptable.
> Has there been a decision on the directory structure yet, or is that likely to be something that will need resolved at the next Stewards Meeting?
Based on the discussion thus far, I'd suggest
"OvmfPkg/SecondClass/Bhyve". If you have the time, just go ahead and
submit the series like that, and wait for review.
If you'd first like to be sure that everyone's OK with this pathname,
then please wait for more feedback in this thread.
Thanks
Laszlo
next prev parent reply other threads:[~2020-05-15 9:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 15:44 Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg? Rebecca Cran
2020-05-11 15:55 ` Laszlo Ersek
2020-05-11 16:20 ` Ard Biesheuvel
2020-05-11 16:36 ` Michael D Kinney
2020-05-11 16:38 ` Andrew Fish
2020-05-11 16:41 ` [edk2-devel] " Michael D Kinney
2020-05-11 21:12 ` Laszlo Ersek
2020-05-11 21:22 ` Michael D Kinney
2020-05-11 21:58 ` [edk2-devel] " Rebecca Cran
2020-05-12 9:28 ` Laszlo Ersek
2020-05-12 9:52 ` Ard Biesheuvel
2020-05-12 15:09 ` Laszlo Ersek
2020-05-14 2:34 ` Rebecca Cran
2020-05-14 10:24 ` Laszlo Ersek
2020-05-14 16:20 ` Rebecca Cran
2020-05-14 17:48 ` Sean
2020-05-14 18:22 ` Rebecca Cran
2020-05-14 18:46 ` Sean
2020-05-14 18:54 ` Rebecca Cran
2020-05-15 9:39 ` Laszlo Ersek
2020-05-15 9:42 ` Laszlo Ersek [this message]
2020-05-15 9:47 ` Ard Biesheuvel
2020-05-15 12:51 ` Laszlo Ersek
2020-05-15 15:03 ` Leif Lindholm
2020-05-11 16:25 ` Michael D Kinney
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-list 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=56efcbf5-2fe8-4620-a98c-7b2bb60f0ceb@redhat.com \
--to=devel@edk2.groups.io \
/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