DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Lee Daly <lee.daly@intel.com>
Cc: cristian.dumitresc@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples/ip_pipeline: update copyright and license
Date: Tue, 23 Jan 2018 17:08:22 +0000	[thread overview]
Message-ID: <20180123170821.GA4512@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <1516725865-51450-1-git-send-email-lee.daly@intel.com>

On Tue, Jan 23, 2018 at 04:44:25PM +0000, Lee Daly wrote:
> This updates the Intel, Oliver Matz and Internet Software Consortium
> license on files in examples to be the standard BSD-3-Clause license
> used for the rest of DPDK,bringing the files in compliance with
> the DPDK licensing policy.
> 
> Signed-off-by: Lee Daly <lee.daly@intel.com>
> ---

ISC License is not a BSD-3-Clause license so cannot be replaced here.
Suggest you just replace Intel and Olivier's license and then look to
get Olivier's ack to have it applied. The ISC will have to be dealt with
separately.

/Bruce

  reply	other threads:[~2018-01-23 17:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 14:39 [dpdk-dev] [PATCH] examples: " Lee Daly
2018-01-22 12:48 ` Olivier Matz
2018-01-22 12:57 ` Hemant Agrawal
2018-01-23 16:43 ` [dpdk-dev] [PATCH] examples/cmdline: " Lee Daly
2018-02-07 16:15   ` Ferruh Yigit
2018-02-12 10:16     ` Olivier Matz
2018-02-13 22:25       ` Thomas Monjalon
2018-01-23 16:44 ` [dpdk-dev] [PATCH] examples/ip_pipeline: " Lee Daly
2018-01-23 17:08   ` Bruce Richardson [this message]
2018-01-24 13:20   ` Lee Daly
2018-01-26  9:24     ` Olivier Matz
2018-01-29 13:32     ` [dpdk-dev] [PATCH v2] " Lee Daly
2018-02-07 16:28       ` [dpdk-dev] [PATCH v3] " Lee Daly
2018-02-07 16:43         ` [dpdk-dev] [PATCH v4] " Lee Daly
2018-02-08  8:31           ` Hemant Agrawal
2018-02-12 10:15           ` Olivier Matz
2018-02-13 22:28             ` Thomas Monjalon
2018-01-24 13:27   ` [dpdk-dev] [PATCH] examples: update copyrights " Lee Daly
2018-02-07 16:15     ` Ferruh Yigit
2018-02-07 16:24     ` Jerin Jacob
2018-02-08  8:29     ` Hemant Agrawal
2018-02-08 14:03     ` [dpdk-dev] [PATCH v2] examples/performance-thread: " Lee Daly
2018-02-08 14:55       ` Ferruh Yigit
2018-02-08 21:36         ` Thomas Monjalon
2018-01-23 16:45 ` [dpdk-dev] [PATCH] examples/l3fwd: update copyright " Lee Daly
2018-02-07 16:15   ` Ferruh Yigit
2018-02-08 21:47     ` Thomas Monjalon
2018-01-23 16:45 ` [dpdk-dev] [PATCH] examples/l3fwd: update copyright and licenses Lee Daly
2018-02-07 16:15   ` Ferruh Yigit
2018-02-08  8:35   ` Hemant Agrawal
2018-02-08  8:39     ` Hemant Agrawal
2018-05-25 10:07   ` Thomas Monjalon
2018-01-23 16:46 ` [dpdk-dev] [PATCH] examples: update copyrights and license Lee Daly
2018-01-23 17:09   ` Bruce Richardson
2018-02-08  8:49   ` Hemant Agrawal
2018-02-08 13:48     ` Daly, Lee
2018-02-09  4:55       ` Hemant Agrawal
2018-02-09 14:30         ` Hasan Alayli
2018-02-09 15:09   ` Hemant Agrawal
2018-01-23 16:46 ` [dpdk-dev] [PATCH] examples: update copyrights and licenses Lee Daly
2018-02-08  7:58 ` [dpdk-dev] [PATCH] examples: update copyright and license Chao Zhu

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=20180123170821.GA4512@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=cristian.dumitresc@intel.com \
    --cc=dev@dpdk.org \
    --cc=lee.daly@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).