From: "Laszlo Ersek" <lersek@redhat.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jordan Justen <jordan.l.justen@intel.com>,
Julien Grall <julien.grall@arm.com>,
Lars Kurth <lars.kurth@citrix.com>,
xen-devel@lists.xenproject.org
Subject: [PATCH 2/4] OvmfPkg/License.txt: refresh the MIT license text and include the SPDX ID
Date: Wed, 10 Apr 2019 14:58:07 +0200 [thread overview]
Message-ID: <20190410125809.21985-3-lersek@redhat.com> (raw)
In-Reply-To: <20190410125809.21985-1-lersek@redhat.com>
Refresh the MIT license text from <https://spdx.org/licenses/MIT.html>,
and add "SPDX-License-Identifier: MIT" for easier parsing by machines.
This follows the tree-wide adoption of "SPDX-License-Identifier"s, made
for <https://bugzilla.tianocore.org/show_bug.cgi?id=1373>; in particular:
- commit 304bff7223a8 ("edk2: Change License.txt from 2-Clause BSD to
BSD+Patent", 2019-04-09),
- commit 75fae505b735 ("OvmfPkg: Change License.txt from 2-Clause BSD to
BSD+Patent", 2019-04-09).
Cc: Anthony Perard <anthony.perard@citrix.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Julien Grall <julien.grall@arm.com>
Cc: Lars Kurth <lars.kurth@citrix.com>
Cc: xen-devel@lists.xenproject.org
Bugzilla: https://bugzilla.tianocore.org/show_bug.cgi?id=1654
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
---
OvmfPkg/License.txt | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/OvmfPkg/License.txt b/OvmfPkg/License.txt
index a2e02a1796aa..6ec950cd9e13 100644
--- a/OvmfPkg/License.txt
+++ b/OvmfPkg/License.txt
@@ -55,19 +55,22 @@ POSSIBILITY OF SUCH DAMAGE.
Some files are subject to the following license, the MIT license. Those files
are located in:
- OvmfPkg/Include/IndustryStandard/Xen/
- OvmfPkg/XenBusDxe/
+SPDX-License-Identifier: MIT
+
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
+The above copyright notice and this permission notice (including the next
+paragraph) shall be included in all copies or substantial portions of the
+Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
--
2.19.1.3.g30247aa5d201
next prev parent reply other threads:[~2019-04-10 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 12:58 [PATCH 0/4] OvmfPkg: replace MIT license blocks with SPDX IDs Laszlo Ersek
2019-04-10 12:58 ` [PATCH 1/4] OvmfPkg/License.txt: remove XenPvBlkDxe from the MIT licensed dir list Laszlo Ersek
2019-04-10 12:58 ` Laszlo Ersek [this message]
2019-04-11 10:34 ` [edk2-devel] [PATCH 2/4] OvmfPkg/License.txt: refresh the MIT license text and include the SPDX ID Philippe Mathieu-Daudé
2019-04-10 12:58 ` [PATCH 3/4] OvmfPkg/IndustryStandard/Xen: replace MIT license text with " Laszlo Ersek
2019-04-10 12:58 ` [PATCH 4/4] OvmfPkg/XenBusDxe: " Laszlo Ersek
2019-04-10 16:23 ` [PATCH 0/4] OvmfPkg: replace MIT license blocks with SPDX IDs Ard Biesheuvel
2019-04-11 10:33 ` Anthony PERARD
2019-04-12 10:06 ` [edk2-devel] " 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=20190410125809.21985-3-lersek@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