From: "Laszlo Ersek" <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@arm.com>,
Rebecca Cran <rebecca@bsdio.com>,
devel@edk2.groups.io, michael.d.kinney@intel.com
Cc: Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>
Subject: Re: [edk2-devel] Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg?
Date: Tue, 12 May 2020 17:09:45 +0200 [thread overview]
Message-ID: <671a668a-fa5c-af15-c208-2d4ae64254ae@redhat.com> (raw)
In-Reply-To: <c4b6a53e-06b3-6a68-fa85-d043f5946457@arm.com>
On 05/12/20 11:52, Ard Biesheuvel wrote:
> If nobody is invested enough in a platform to notice that is gets
> broken, I don't think we should put the burden on other maintainers to
> take responsibility for that.
I meant to say the same thing.
(I could try to explain how your words map -- IMO -- 1:1 to my
UefiCpuPkg example, but I guess I won't risk even more confusion. So
I'll just say "I agree".)
Thanks
Laszlo
next prev parent reply other threads:[~2020-05-12 15:09 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 [this message]
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
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=671a668a-fa5c-af15-c208-2d4ae64254ae@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