public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, Laszlo Ersek <lersek@redhat.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Michael Kinney <michael.d.kinney@intel.com>,
	Andrew Fish <afish@apple.com>, Peter Grehan <grehan@freebsd.org>
Subject: Re: [edk2-devel] [PATCH v3 4/6] Add BhyvePkg, to support the bhyve hypervisor
Date: Thu, 23 Apr 2020 14:08:21 -0600	[thread overview]
Message-ID: <E3BFFBA9-2EF3-461B-9EE4-F9558EB0976E@bsdio.com> (raw)
In-Reply-To: <e39cd8ea-9071-7f42-30f4-bb4c0d538363@redhat.com>


> On Apr 23, 2020, at 3:19 AM, Laszlo Ersek <lersek@redhat.com> wrote:
> 
> (2) If you are contributing this new file in "Pluribus Networks, Inc"
> colors, then please extend the year to 2020 on that line. Otherwise, if
> you are contributing this on your own behalf (as work derived from
> Pluribus Networks's earlier work), then please add your own (C) on top
> as well, marking the year 2020.
> 
> My point is that the year is 2020, when this file is being introduced in
> edk2. Thus, there should be a (C) notice naming the year 2020.

Unfortunately I’m not contributing for Pluribus Networks — that’s why we have to keep some files are BSD-2-Clause.
Should I add my own copyright line for _all_ files I’m adding under BhyvePkg, or just those that have new/changed content? For example there are several files such as BhyvePkg/PlatformPei/AmdSev.c that I copied verbatim from OvmfPkg that I’d feel especially uncomfortable with claiming copyright over.

> (9) I think we should delete the MIT license. At this stage, I can't see
> anything MIT-covered under BhyvePkg. Do you agree?

Yes, I agree. I’ll proceed with that change.

— 
Rebecca Cran



  parent reply	other threads:[~2020-04-23 20:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21  3:09 [PATCH v3 0/6] Add BhyvePkg, to support the bhyve hypervisor Rebecca Cran
2020-04-21  3:09 ` [PATCH v3 1/6] OvmfPkg: Add bhyve support into AcpiTimerLib Rebecca Cran
2020-04-23  7:56   ` [edk2-devel] " Laszlo Ersek
2020-04-21  3:09 ` [PATCH v3 2/6] OvmfPkg: Add QemuFwCfgLibNull Rebecca Cran
2020-04-23  8:21   ` [edk2-devel] " Laszlo Ersek
2020-04-21  3:09 ` [PATCH v3 3/6] OvmfPkg: Add VBE2 mode info structure to LegacyVgaBios.h Rebecca Cran
2020-04-23  8:05   ` [edk2-devel] " Laszlo Ersek
2020-04-21  3:09 ` [PATCH v3 4/6] Add BhyvePkg, to support the bhyve hypervisor Rebecca Cran
2020-04-23  9:19   ` [edk2-devel] " Laszlo Ersek
2020-04-23  9:42     ` Laszlo Ersek
2020-04-24  5:54       ` Rebecca Cran
2020-04-24 12:22         ` Laszlo Ersek
2020-04-23 20:08     ` Rebecca Cran [this message]
2020-04-24 10:11       ` Laszlo Ersek
2020-04-24 16:00         ` Rebecca Cran
2020-04-21  3:09 ` [PATCH v3 5/6] BhyvePkg: Add PlatformPei Rebecca Cran
2020-04-23  9:24   ` [edk2-devel] " Laszlo Ersek
2020-04-21  3:09 ` [PATCH v3 6/6] BhyvePkg: Add AcpiPlatformDxe Rebecca Cran
2020-04-23  9:44   ` [edk2-devel] " Laszlo Ersek
2020-04-21 15:27 ` [PATCH v3 0/6] Add BhyvePkg, to support the bhyve hypervisor Laszlo Ersek
2020-04-21 15:38   ` Rebecca Cran
2020-04-22 15:21     ` Laszlo Ersek
2020-04-22 16:48       ` Rebecca Cran
2020-04-24 10:11         ` 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-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=E3BFFBA9-2EF3-461B-9EE4-F9558EB0976E@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