From: Roland Hieber <rhi@pengutronix.de>
To: oss-tools@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [OSS-Tools] [PATCH dt-utils v2 8/9] DCO: add SPDX license information
Date: Mon, 31 Jul 2023 11:11:30 +0200 [thread overview]
Message-ID: <20230731091131.3696307-9-rhi@pengutronix.de> (raw)
In-Reply-To: <20230731091131.3696307-1-rhi@pengutronix.de>
There is nothing prefabricated yet, so use a custom LicenseRef instead.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
PATCH v2: new in series v2
---
DCO | 2 ++
LICENSES/LicenseRef-DCO.txt | 2 ++
2 files changed, 4 insertions(+)
create mode 100644 LICENSES/LicenseRef-DCO.txt
diff --git a/DCO b/DCO
index 8201f992154a..75e56dd2683f 100644
--- a/DCO
+++ b/DCO
@@ -1,3 +1,5 @@
+# SPDX-License-Identifier: LicenseRef-DCO
+
Developer Certificate of Origin
Version 1.1
diff --git a/LICENSES/LicenseRef-DCO.txt b/LICENSES/LicenseRef-DCO.txt
new file mode 100644
index 000000000000..b5b12d7c360b
--- /dev/null
+++ b/LICENSES/LicenseRef-DCO.txt
@@ -0,0 +1,2 @@
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
--
2.39.2
next prev parent reply other threads:[~2023-07-31 9:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 9:11 [OSS-Tools] [PATCH dt-utils v2 0/9] make project conform to the REUSE specification Roland Hieber
2023-07-31 9:11 ` [OSS-Tools] [PATCH dt-utils v2 1/9] treewide: add SPDX identifiers to files with GPL-2.0-only license Roland Hieber
2023-07-31 9:40 ` Ahmad Fatoum
2023-07-31 9:11 ` [OSS-Tools] [PATCH dt-utils v2 2/9] treewide: add SPDX identifiers to files with GPL-2.0-or-later license Roland Hieber
2023-07-31 9:41 ` Ahmad Fatoum
2023-07-31 9:11 ` [OSS-Tools] [PATCH dt-utils v2 3/9] treewide: add SPDX identifiers to files with GPL-3.0-or-later license Roland Hieber
2023-07-31 9:41 ` Ahmad Fatoum
2023-07-31 9:11 ` [OSS-Tools] [PATCH dt-utils v2 4/9] treewide: add SPDX identifier to file with Zlib license Roland Hieber
2023-07-31 9:42 ` Ahmad Fatoum
2023-07-31 9:11 ` [OSS-Tools] [PATCH dt-utils v2 5/9] treewide: add CC0-1.0 SPDX identifiers for trivial files Roland Hieber
2023-07-31 9:43 ` Ahmad Fatoum
2023-07-31 9:11 ` [OSS-Tools] [PATCH dt-utils v2 6/9] treewide: add GPL-2.0-only SPDX identifiers to files without license Roland Hieber
2023-07-31 9:44 ` Ahmad Fatoum
2023-07-31 9:11 ` [OSS-Tools] [PATCH dt-utils v2 7/9] treewide: add trivial copyright headers Roland Hieber
2023-07-31 9:44 ` Ahmad Fatoum
2023-07-31 9:11 ` Roland Hieber [this message]
2023-07-31 9:45 ` [OSS-Tools] [PATCH dt-utils v2 8/9] DCO: add SPDX license information Ahmad Fatoum
2023-07-31 9:11 ` [OSS-Tools] [PATCH dt-utils v2 9/9] README: mention compatibility with the REUSE specification Roland Hieber
2023-07-31 9:45 ` Ahmad Fatoum
2023-08-01 10:10 ` [OSS-Tools] [PATCH dt-utils v2 0/9] make project conform to " Roland Hieber
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=20230731091131.3696307-9-rhi@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=oss-tools@pengutronix.de \
/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