From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Marko Kovacevic <marko.kovacevic@intel.com>,
dev@dpdk.org, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] doc: add SPDX Licence to doc files
Date: Tue, 10 Apr 2018 10:08:47 +0530 [thread overview]
Message-ID: <9d6e8082-341b-3ff5-9918-82a4bc9e149d@nxp.com> (raw)
In-Reply-To: <a32d98be-ccbb-8dad-388f-f4d10f093118@intel.com>
On 4/9/2018 7:24 PM, Ferruh Yigit wrote:
> On 4/9/2018 2:11 PM, Marko Kovacevic wrote:
>> Added SPDX headers to doc files to have them aligned with
>> the other doc files.
>>
>> Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
>
> <...>
>
>> doc/guides/rel_notes/release_16_04.rst | 3 +++
>> doc/guides/rel_notes/release_16_07.rst | 3 +++
>> doc/guides/rel_notes/release_16_11.rst | 3 +++
>> doc/guides/rel_notes/release_17_02.rst | 3 +++
>> doc/guides/rel_notes/release_17_05.rst | 3 +++
>> doc/guides/rel_notes/release_17_08.rst | 3 +++
>> doc/guides/rel_notes/release_17_11.rst | 3 +++
>> doc/guides/rel_notes/release_18_02.rst | 3 +++
>> doc/guides/rel_notes/release_2_2.rst | 3 +++
>
> Hi Hemant,
>
> What does it mean to have a license header in release notes?
> It looks unnecessary from both license and copyright point of view, is there a
> legal requirement for it?
>
> Indeed I was thinking removing the header from the release notes that has it...
LF legal reported it as missing license. All other *.rst files have the
license headers.
Let me check it with LF Legal.
Regards,
Hemant
>
> Thanks,
> ferruh
>
next prev parent reply other threads:[~2018-04-10 4:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 13:11 Marko Kovacevic
2018-04-09 13:54 ` Ferruh Yigit
2018-04-10 4:38 ` Hemant Agrawal [this message]
2018-05-25 10:39 ` Thomas Monjalon
2018-05-25 15:30 ` Kovacevic, Marko
2018-05-26 12:58 ` Hemant Agrawal
2018-05-28 16:08 ` Mcnamara, John
2018-05-29 3:25 ` Hemant Agrawal
2018-05-29 17:05 ` Mcnamara, John
2018-05-30 15:18 ` Kovacevic, Marko
2018-05-30 15:26 ` Ferruh Yigit
2018-05-31 6:39 ` Hemant Agrawal
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=9d6e8082-341b-3ff5-9918-82a4bc9e149d@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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).