From: "Alex Bennée" <alex.bennee@linaro.org>
To: u-boot@lists.denx.de
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: [RFC PATCH] link principle license to COPYING
Date: Mon, 29 Sep 2025 16:51:42 +0100 [thread overview]
Message-ID: <20250929155142.1647606-1-alex.bennee@linaro.org> (raw)
Some license scanners are particularly dumb and when combined with
automatic license scanning for FLOSS accreditation on forges cause
problems on renewal. As GPL 2.0 applies to the core code link the main
licence text to COPYING to keep everything happy.
This caused issues for the QEMU project recently as we mirror (two!)
copies of u-boot in our project.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
COPYING | 1 +
1 file changed, 1 insertion(+)
create mode 120000 COPYING
diff --git a/COPYING b/COPYING
new file mode 120000
index 00000000000..1ed3ba6a13c
--- /dev/null
+++ b/COPYING
@@ -0,0 +1 @@
+Licenses/gpl-2.0.txt
\ No newline at end of file
--
2.47.3
next reply other threads:[~2025-09-29 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 15:51 Alex Bennée [this message]
2025-09-29 16:50 ` [RFC PATCH] link principle license to COPYING Tom Rini
2025-09-29 18:08 ` Alex Bennée
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=20250929155142.1647606-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=u-boot@lists.denx.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;
as well as URLs for NNTP newsgroup(s).