From: Stephen Hemminger <stephen@networkplumber.org>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] devtools: add SPDX license tag check script
Date: Mon, 16 Dec 2019 13:58:05 -0800 [thread overview]
Message-ID: <20191216135805.27ed2684@hermes.lan> (raw)
In-Reply-To: <VI1PR0401MB25418C18CDAA0F4D9E3E0F5B89760@VI1PR0401MB2541.eurprd04.prod.outlook.com>
On Wed, 13 Nov 2019 06:59:48 +0000
Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
> HI Stephen,
> Will you please enhance it to also provide number of files in each category?
>
> We also need to think about how to handle the scripts "*.sh", as many of these are without SPDX.
> - we can either leave them as it is.
> Or , we can put the SPDX header without a copyright?
>
> Regards,
> Hemant
The shell files are covered and only a 3 files had missing headers.
Patches are in patchwork for these.
The copyright is better if present, but without it we can infer the copyright
from the original author in git.
The goal is to get this to 0, so that they output is nothing...
Then add it to CI.
prev parent reply other threads:[~2019-12-16 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 16:43 [dpdk-dev] [RFC] devtools: add spdx license check tool Stephen Hemminger
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 [this message]
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=20191216135805.27ed2684@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
/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).