From: Kevin Traynor <ktraynor@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>,
John McNamara <john.mcnamara@intel.com>,
bluca@debian.org
Cc: dev@dpdk.org, ferruh.yigit@intel.com,
Bruce Richardson <bruce.richardson@intel.com>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] license: add licenses for exception cases
Date: Fri, 11 Dec 2020 12:49:19 +0000 [thread overview]
Message-ID: <1bc3d17c-b556-24db-6760-4f0a09903e5a@redhat.com> (raw)
In-Reply-To: <1658595.gB0cm55zWW@thomas>
On 11/12/2020 11:24, Thomas Monjalon wrote:
> 11/12/2020 12:20, Thomas Monjalon:
>> 03/12/2020 10:43, Bruce Richardson:
>>> On Wed, Dec 02, 2020 at 07:01:40PM +0000, John McNamara wrote:
>>>> The license/exceptions.txt file lists a small number of files
>>>> that have licenses that are exceptions to the three main
>>>> licenses defined in the Intellectual Property Policy of the
>>>> DPDK Charter.
>>>>
>>>> The three exception licenses are MIT, ISC and BSD-2-Clause.
>>>> Each of these licenses states that the content of the license
>>>> message should be included in the code distribution. This
>>>> change adds the text of the MIT, ISC and BSD-2-Clause licenses
>>>> as defined on the SPDX website.
>>>>
>>>> Signed-off-by: John McNamara <john.mcnamara@intel.com>
>>>> ---
>>> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>>
>> Applied, thanks
>
> Added Cc stable to be compliant with the licenses in 18.11 and 19.11.
>
>
Applied to 18.11 branch, thanks.
next prev parent reply other threads:[~2020-12-11 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201201142646.2522769-1-john.mcnamara@intel.com>
[not found] ` <20201203094300.GA1625@bricha3-MOBL.ger.corp.intel.com>
[not found] ` <1901524.QUgt7jSOqn@thomas>
2020-12-11 11:24 ` Thomas Monjalon
2020-12-11 12:49 ` Kevin Traynor [this message]
2020-12-11 13:36 ` Luca Boccassi
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=1bc3d17c-b556-24db-6760-4f0a09903e5a@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).