From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
Wei Liu <wl@xen.org>, Julien Grall <julien@xen.org>
Subject: [PATCH 1/2] LICENSES: Improve the legibility of these files
Date: Fri, 5 May 2023 14:05:32 +0100 [thread overview]
Message-ID: <20230505130533.3580545-2-andrew.cooper3@citrix.com> (raw)
In-Reply-To: <20230505130533.3580545-1-andrew.cooper3@citrix.com>
A few newlines go a very long way
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
---
CC: George Dunlap <George.Dunlap@eu.citrix.com>
CC: Jan Beulich <JBeulich@suse.com>
CC: Stefano Stabellini <sstabellini@kernel.org>
CC: Wei Liu <wl@xen.org>
CC: Julien Grall <julien@xen.org>
---
LICENSES/BSD-2-Clause | 4 ++++
LICENSES/BSD-3-Clause | 4 ++++
LICENSES/BSD-3-Clause-Clear | 4 ++++
LICENSES/CC-BY-4.0 | 5 +++++
LICENSES/GPL-2.0 | 5 +++++
LICENSES/LGPL-2.0 | 6 ++++++
LICENSES/LGPL-2.1 | 6 ++++++
LICENSES/MIT | 4 ++++
8 files changed, 38 insertions(+)
diff --git a/LICENSES/BSD-2-Clause b/LICENSES/BSD-2-Clause
index da366e2ce50b..694d8c93221c 100644
--- a/LICENSES/BSD-2-Clause
+++ b/LICENSES/BSD-2-Clause
@@ -1,10 +1,14 @@
Valid-License-Identifier: BSD-2-Clause
+
SPDX-URL: https://spdx.org/licenses/BSD-2-Clause.html
+
Usage-Guide:
+
To use the BSD 2-clause "Simplified" License put the following SPDX
tag/value pair into a comment according to the placement guidelines in
the licensing rules documentation:
SPDX-License-Identifier: BSD-2-Clause
+
License-Text:
Copyright (c) <year> <owner> . All rights reserved.
diff --git a/LICENSES/BSD-3-Clause b/LICENSES/BSD-3-Clause
index 34c7f057c8d5..1441947f92e0 100644
--- a/LICENSES/BSD-3-Clause
+++ b/LICENSES/BSD-3-Clause
@@ -1,10 +1,14 @@
Valid-License-Identifier: BSD-3-Clause
+
SPDX-URL: https://spdx.org/licenses/BSD-3-Clause.html
+
Usage-Guide:
+
To use the BSD 3-clause "New" or "Revised" License put the following SPDX
tag/value pair into a comment according to the placement guidelines in
the licensing rules documentation:
SPDX-License-Identifier: BSD-3-Clause
+
License-Text:
Copyright (c) <year> <owner> . All rights reserved.
diff --git a/LICENSES/BSD-3-Clause-Clear b/LICENSES/BSD-3-Clause-Clear
index e53b56092b90..2b27f24a65a0 100644
--- a/LICENSES/BSD-3-Clause-Clear
+++ b/LICENSES/BSD-3-Clause-Clear
@@ -1,10 +1,14 @@
Valid-License-Identifier: BSD-3-Clause-Clear
+
SPDX-URL: https://spdx.org/licenses/BSD-3-Clause-Clear.html
+
Usage-Guide:
+
To use the BSD 3-clause "Clear" License put the following SPDX
tag/value pair into a comment according to the placement guidelines in
the licensing rules documentation:
SPDX-License-Identifier: BSD-3-Clause-Clear
+
License-Text:
The Clear BSD License
diff --git a/LICENSES/CC-BY-4.0 b/LICENSES/CC-BY-4.0
index 27dfefa95ccf..4197ceb180ff 100644
--- a/LICENSES/CC-BY-4.0
+++ b/LICENSES/CC-BY-4.0
@@ -1,15 +1,20 @@
Valid-License-Identifier: CC-BY-4.0
+
SPDX-URL: https://spdx.org/licenses/CC-BY-4.0
+
Usage-Guide:
+
Do NOT use this license for code, but it's acceptable for content like artwork
or documentation. When using it for the latter, it's best to use it together
with a GPL2 compatible license using "OR", as CC-BY-4.0 texts processed by
the kernel's build system might combine it with content taken from more
restrictive licenses.
+
To use the Creative Commons Attribution 4.0 International license put
the following SPDX tag/value pair into a comment according to the
placement guidelines in the licensing rules documentation:
SPDX-License-Identifier: CC-BY-4.0
+
License-Text:
Creative Commons Attribution 4.0 International
diff --git a/LICENSES/GPL-2.0 b/LICENSES/GPL-2.0
index 9f09528a8bce..0022a7c17788 100644
--- a/LICENSES/GPL-2.0
+++ b/LICENSES/GPL-2.0
@@ -2,11 +2,15 @@ Valid-License-Identifier: GPL-2.0
Valid-License-Identifier: GPL-2.0-only
Valid-License-Identifier: GPL-2.0+
Valid-License-Identifier: GPL-2.0-or-later
+
SPDX-URL: https://spdx.org/licenses/GPL-2.0.html
+
Usage-Guide:
+
To use this license in source code, put one of the following SPDX
tag/value pairs into a comment according to the placement
guidelines in the licensing rules documentation.
+
For 'GNU General Public License (GPL) version 2 only' use:
SPDX-License-Identifier: GPL-2.0-only
or (now deprecated)
@@ -15,6 +19,7 @@ Usage-Guide:
SPDX-License-Identifier: GPL-2.0+
or
SPDX-License-Identifier: GPL-2.0-or-later
+
License-Text:
GNU GENERAL PUBLIC LICENSE
diff --git a/LICENSES/LGPL-2.0 b/LICENSES/LGPL-2.0
index 957d798fe037..2fa16d72eabf 100644
--- a/LICENSES/LGPL-2.0
+++ b/LICENSES/LGPL-2.0
@@ -1,15 +1,21 @@
Valid-License-Identifier: LGPL-2.0
Valid-License-Identifier: LGPL-2.0+
+
SPDX-URL: https://spdx.org/licenses/LGPL-2.0.html
+
Usage-Guide:
+
To use this license in source code, put one of the following SPDX
tag/value pairs into a comment according to the placement
guidelines in the licensing rules documentation.
+
For 'GNU Library General Public License (LGPL) version 2.0 only' use:
SPDX-License-Identifier: LGPL-2.0
+
For 'GNU Library General Public License (LGPL) version 2.0 or any later
version' use:
SPDX-License-Identifier: LGPL-2.0+
+
License-Text:
GNU LIBRARY GENERAL PUBLIC LICENSE
diff --git a/LICENSES/LGPL-2.1 b/LICENSES/LGPL-2.1
index 27bb4342a3e8..b366c7e49199 100644
--- a/LICENSES/LGPL-2.1
+++ b/LICENSES/LGPL-2.1
@@ -1,15 +1,21 @@
Valid-License-Identifier: LGPL-2.1
Valid-License-Identifier: LGPL-2.1+
+
SPDX-URL: https://spdx.org/licenses/LGPL-2.1.html
+
Usage-Guide:
+
To use this license in source code, put one of the following SPDX
tag/value pairs into a comment according to the placement
guidelines in the licensing rules documentation.
+
For 'GNU Lesser General Public License (LGPL) version 2.1 only' use:
SPDX-License-Identifier: LGPL-2.1
+
For 'GNU Lesser General Public License (LGPL) version 2.1 or any later
version' use:
SPDX-License-Identifier: LGPL-2.1+
+
License-Text:
GNU LESSER GENERAL PUBLIC LICENSE
diff --git a/LICENSES/MIT b/LICENSES/MIT
index f33a68ceb3ea..eba1549f93e4 100644
--- a/LICENSES/MIT
+++ b/LICENSES/MIT
@@ -1,10 +1,14 @@
Valid-License-Identifier: MIT
+
SPDX-URL: https://spdx.org/licenses/MIT.html
+
Usage-Guide:
+
To use the MIT License put the following SPDX tag/value pair into a
comment according to the placement guidelines in the licensing rules
documentation:
SPDX-License-Identifier: MIT
+
License-Text:
MIT License
--
2.30.2
next prev parent reply other threads:[~2023-05-05 13:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 13:05 [PATCH 0/2] LICENSES improvements/corrections Andrew Cooper
2023-05-05 13:05 ` Andrew Cooper [this message]
2023-05-05 13:06 ` [PATCH 1/2] LICENSES: Improve the legibility of these files Jan Beulich
2023-05-05 22:29 ` Stefano Stabellini
2023-05-05 13:05 ` [PATCH 2/2] LICENSES: Remove the use of deprecated LGPL SPDX tags Andrew Cooper
2023-05-05 13:13 ` Jan Beulich
2023-05-05 13:22 ` Andrew Cooper
2023-05-05 13:31 ` Jan Beulich
2023-05-05 13:36 ` Andrew Cooper
2023-05-05 15:30 ` Anthony PERARD
2023-05-05 15:52 ` Andrew Cooper
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-all 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=20230505130533.3580545-2-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.