From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/8] replace BSD headers with SPDX tags
Date: Thu, 04 Jan 2018 22:11:47 +0100 [thread overview]
Message-ID: <1770768.mazYbQRNiY@xps> (raw)
In-Reply-To: <20171219154906.227759-1-bruce.richardson@intel.com>
19/12/2017 16:48, Bruce Richardson:
> Similar to what was done with the .c and .h files, replace BSD license
> headers on makefiles and script files which were copyright by Intel alone.
>
> Bruce Richardson (8):
> app: add SPDX tags for Intel copyright Makefiles
> tools: add SPDX tags for Intel copyright scripts
> drivers: add SPDX tags for Intel copyright Makefiles
> examples: add SPDX tags for Intel copyright Makefiles
> lib: add SPDX tags for Intel copyright Makefiles
> mk: add SPDX tags for Intel copyright Makefiles
> test: add SPDX tags for Intel copyright Makefiles
> doc: add SPDX tag for Intel copyright file
Applied and merged with .c/.h changes.
prev parent reply other threads:[~2018-01-04 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 15:48 [PATCH 0/8] replace BSD headers with SPDX tags Bruce Richardson
2017-12-19 15:48 ` [PATCH 1/8] app: add SPDX tags for Intel copyright Makefiles Bruce Richardson
2017-12-19 15:49 ` [PATCH 2/8] tools: add SPDX tags for Intel copyright scripts Bruce Richardson
2017-12-19 15:49 ` [PATCH 3/8] drivers: add SPDX tags for Intel copyright Makefiles Bruce Richardson
2017-12-19 15:49 ` [PATCH 4/8] examples: " Bruce Richardson
2017-12-19 15:49 ` [PATCH 5/8] lib: " Bruce Richardson
2017-12-19 15:49 ` [PATCH 6/8] mk: " Bruce Richardson
2017-12-19 15:49 ` [PATCH 7/8] test: " Bruce Richardson
2017-12-19 15:49 ` [PATCH 8/8] doc: add SPDX tag for Intel copyright file Bruce Richardson
2017-12-19 16:02 ` [PATCH 0/8] replace BSD headers with SPDX tags Stephen Hemminger
2018-01-04 21:11 ` Thomas Monjalon [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=1770768.mazYbQRNiY@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--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 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.