From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [RFC] devtools: add spdx license check tool
Date: Wed, 14 Aug 2019 09:43:20 -0700 [thread overview]
Message-ID: <20190814164320.12376-1-stephen@networkplumber.org> (raw)
This is a simple script to print files that have missing SPDX
license tag and list of files with redundant boilerplate.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
devtools/spdx-check.sh | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
create mode 100755 devtools/spdx-check.sh
diff --git a/devtools/spdx-check.sh b/devtools/spdx-check.sh
new file mode 100755
index 000000000000..c77454a8b320
--- /dev/null
+++ b/devtools/spdx-check.sh
@@ -0,0 +1,19 @@
+#! /bin/sh
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright (c) 2019 Microsoft Corporation
+#
+# Produce a list of files without SPDX license identifiers
+
+echo "Files without SPDX License"
+echo "--------------------------"
+
+git grep -L SPDX-License-Identifier | \
+ grep -v '^\.' |grep -v '^license/' |\
+ grep -v '\.map$' | grep -v '\.png$' | grep -v '\.svg$'
+
+echo
+echo "Files with redundant BSD boilerplate"
+echo "------------------------------------"
+
+git grep -l SPDX-License-Identifier | \
+ xargs grep -l 'Redistribution and use'
--
2.20.1
next reply other threads:[~2019-08-14 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 16:43 Stephen Hemminger [this message]
2019-11-08 17:23 ` [dpdk-dev] [PATCH] devtools: add SPDX license tag check script Stephen Hemminger
2019-11-13 6:56 ` Hemant Agrawal
2019-11-13 6:59 ` Hemant Agrawal
2019-11-13 17:07 ` Stephen Hemminger
2019-12-16 21:58 ` Stephen Hemminger
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=20190814164320.12376-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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 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).