public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Rebecca Cran <rebecca@bsdio.com>,
	edk2-devel-groups-io <devel@edk2.groups.io>
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
	"Justen, Jordan L" <jordan.l.justen@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: OvmfPkg: Adding support for bhyve as OvmfPkg/Bhyve
Date: Fri, 3 Jul 2020 17:50:27 +0200	[thread overview]
Message-ID: <e528ab33-92c3-0bc8-64ab-161afd52081b@redhat.com> (raw)
In-Reply-To: <2b4c5f09-c371-28ba-8135-409a3b770905@bsdio.com>

On 07/03/20 05:13, Rebecca Cran wrote:
> On 7/2/20 3:27 AM, Laszlo Ersek wrote:
> 
>> I'll look at the patches on the list. (I don't believe in reviewing
>> before reviewing. In case I need to make comments for what I find in
>> your repo, I could only make them without any context to quote.)
> 
> Thanks, I'll wait for the changes to PatchCheck.py to land, then send
> the bhyve patch to the list. I think at this point I've updated all the
> licenses to be BSD+Patent with the exception of the generated file.

Sounds great!
Laszlo


      reply	other threads:[~2020-07-03 15:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 15:38 OvmfPkg: Adding support for bhyve as OvmfPkg/Bhyve Rebecca Cran
2020-07-02  9:27 ` Laszlo Ersek
2020-07-02 10:54   ` License Check - was " Leif Lindholm
2020-07-02 13:49     ` [edk2-devel] " Liming Gao
2020-07-02 14:13       ` Leif Lindholm
2020-07-02 14:31         ` Ard Biesheuvel
2020-07-03  1:40           ` Liming Gao
2020-07-03 10:37             ` Leif Lindholm
2020-07-03 15:07               ` Liming Gao
2020-07-03 15:49             ` Laszlo Ersek
2020-07-07 14:31               ` Liming Gao
2020-07-03  3:13   ` Rebecca Cran
2020-07-03 15:50     ` 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-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=e528ab33-92c3-0bc8-64ab-161afd52081b@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