From: "Rebecca Cran" <rebecca@bsdio.com>
To: Sean Brogan <spbrogan@outlook.com>,
devel@edk2.groups.io, lersek@redhat.com
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: Thu, 14 May 2020 12:22:31 -0600 [thread overview]
Message-ID: <39f882ec-c7ba-0abe-7100-e4d3b9c78678@bsdio.com> (raw)
In-Reply-To: <BN8PR07MB69628EC8992C6C230213EB5BC8BC0@BN8PR07MB6962.namprd07.prod.outlook.com>
On 5/14/20 11:48 AM, Sean Brogan wrote:
> Adding another platform to a core repository that might or might not
> work at any given time is a burden to all core contributors and
> doesn't bring value to the core project.
>
> The direction I would like to see is a new repo created at
> github.com/tianocore/Bhyve_Platform.git
Given I'm a FreeBSD committer but not a TianoCore maintainer, I think
I'd prefer to just keep using github.com/freebsd/uefi-edk2.git as the
location for bhyve sources in that case, since it's already set up and I
have commit access to it.
At this point I'm keen to move on from discussing where the code should
live, since I'd like to get my changes committed wherever and start
creating builds for people who are waiting for them and improve bhyve
support in edk2.
--
Rebecca Cran
next prev parent reply other threads:[~2020-05-14 18:22 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 [this message]
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
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=39f882ec-c7ba-0abe-7100-e4d3b9c78678@bsdio.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