From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] license: add licenses for exception cases
Date: Tue, 1 Dec 2020 15:07:22 +0000 [thread overview]
Message-ID: <SN6PR11MB3086D45F0EA1DE6FDEBA445AFCF40@SN6PR11MB3086.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20201201143435.GB1257@bricha3-MOBL.ger.corp.intel.com>
> -----Original Message-----
> From: Bruce Richardson <bruce.richardson@intel.com>
> Sent: Tuesday, December 1, 2020 2:35 PM
> To: Mcnamara, John <john.mcnamara@intel.com>
> Cc: dev@dpdk.org; thomas@monjalon.net; Yigit, Ferruh
> <ferruh.yigit@intel.com>
> Subject: Re: [PATCH v1] license: add licenses for exception cases
>
> ...
>
> The licenses seem to me like they should be included in our packages, since
> each refers to including the license.
> However, for the patch, I think we need properly word-wrapped versions that
> are easy enough to read in raw text form.
I was going to word wrap them but this was the format they were in on the SPDX website and also the existing license/bsd-3-clause.txt is in this (long line) format.
Nevertheless I'll wrap them in the next version to make them more readable.
next prev parent reply other threads:[~2020-12-01 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 14:26 John McNamara
2020-12-01 14:34 ` Bruce Richardson
2020-12-01 15:07 ` Mcnamara, John [this message]
2020-12-02 19:01 ` [dpdk-dev] [PATCH v2] " John McNamara
2020-12-03 9:43 ` Bruce Richardson
2020-12-11 11:20 ` Thomas Monjalon
2020-12-11 11:24 ` Thomas Monjalon
2020-12-11 12:49 ` Kevin Traynor
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=SN6PR11MB3086D45F0EA1DE6FDEBA445AFCF40@SN6PR11MB3086.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).