From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [edk2] [PATCH V3] Change EDK II to BSD+Patent License
Date: Mon, 8 Apr 2019 16:57:10 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9C8A768@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <ab483cec-c970-3755-6ad5-25b6458391cb@redhat.com>
Laszlo,
I agree dates should be consistent. For these
types of dates, I think the commit date is the
better choice. I will change July 18 to Aug 3.
Thanks,
Mike
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Monday, April 8, 2019 5:13 AM
> To: devel@edk2.groups.io; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Subject: Re: [edk2-devel] [edk2] [PATCH V3] Change EDK
> II to BSD+Patent License
>
> On 04/04/19 01:42, Michael D Kinney wrote:
>
> > 17a33094a9 edk2: Add License-History.txt
>
> I have a minuscule comment for this patch.
>
> In the "Key Dates" section, you list two dates:
> - July 18, 2017
> - April 9, 2019
>
> The 2nd date refers to a commit (that is, not patch
> authorship) date. I
> think that's fine.
>
> The first date however refers to a patch authorship
> date, not a commit
> date. I don't feel too strongly about this, but I think
> the consistency
> could be improved.
>
> In particular, from the commits listed in
> <https://bugzilla.tianocore.org/show_bug.cgi?id=629#c3>
> , the most
> relevant seems to be b6538c118ae8. The authorship date
> on that patch is
> indeed 2017-07-18; however its commit date is 2017-08-
> 03.
>
> If, for one of the "key dates" above, we use a "commit
> date" (and not an
> "authorship date"), then we might want to do the same
> for the other "key
> date" (i.e., we might want to replace "July 18, 2017"
> with "August 3,
> 2017").
>
> Anyway, I'll leave it up to you; I'm fine with the
> patch as-is.
>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>
>
> > 8ee83c5dcd edk2: Change License.txt from 2-Clause BSD
> to BSD+Patent
>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>
>
> > bc61733285 edk2: Replace BSD License with BSD+Patent
> License
>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>
>
> > eece5f8a6e edk2: Remove Contributions.txt and update
> Readme.md
>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>
> Thanks
> Laszlo
next prev parent reply other threads:[~2019-04-08 16:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 23:42 [edk2] [PATCH V3] Change EDK II to BSD+Patent License Michael D Kinney
2019-04-04 12:27 ` [edk2-devel] " Laszlo Ersek
2019-04-04 22:27 ` Ma, Maurice
2019-04-05 9:40 ` Ni, Ray
2019-04-05 21:39 ` Michael D Kinney
2019-04-08 1:21 ` [edk2-devel] " Ni, Ray
2019-04-08 1:41 ` Wu, Hao A
2019-04-08 1:44 ` Dong, Eric
2019-04-08 1:50 ` Wu, Hao A
[not found] ` <B80AF82E9BFB8E4FBD8C89DA810C6A093C8BCAAE@SHSMSX104.ccr.corp.intel.com>
[not found] ` <7CB7EF03E15B5D48981329A508747A9850C4FB75@SHSMSX104.ccr.corp.intel.com>
2019-04-08 5:20 ` yi.qian
2019-04-08 9:01 ` Sun, Zailiang
2019-04-08 20:25 ` Michael D Kinney
2019-04-09 9:46 ` [edk2-devel] " Laszlo Ersek
[not found] ` <E92EE9817A31E24EB0585FDF735412F5B9C8A6A3@ORSMSX113.amr.corp.intel.com>
[not found] ` <DB6PR0802MB2375A8D702667DC83C2AAC07842D0@DB6PR0802MB2375.eurprd08.prod.outlook.com>
2019-04-09 18:43 ` Michael D Kinney
[not found] ` <E92EE9817A31E24EB0585FDF735412F5B9C8D207@ORSMSX113.amr.corp.intel.com>
2019-04-09 18:45 ` Sami Mujawar
2019-04-07 23:35 ` Carsey, Jaben
2019-04-08 1:20 ` [edk2-devel] " Siyuan, Fu
2019-04-08 2:04 ` BobCF
2019-04-08 2:31 ` Wang, Jian J
2019-04-08 3:34 ` [edk2-devel] " chasel.chiu
2019-04-08 4:44 ` Liming Gao
2019-04-08 4:46 ` Wang, Jian J
2019-04-08 5:01 ` [edk2-devel] " yi.qian
2019-04-08 5:10 ` Liming Gao
2019-04-08 5:30 ` [edk2-devel] " chasel.chiu
2019-04-08 12:12 ` Laszlo Ersek
2019-04-08 16:57 ` Michael D Kinney [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-08 5:25 zailiang.sun
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=E92EE9817A31E24EB0585FDF735412F5B9C8A768@ORSMSX113.amr.corp.intel.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