From: Olivier MATZ <olivier.matz@6wind.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] net: update licence for network headers
Date: Mon, 11 Dec 2017 09:58:52 +0100 [thread overview]
Message-ID: <20171211085851.4fefe3obd2g7bmbx@platinum> (raw)
In-Reply-To: <448cfe74-224b-8a25-6be3-42c70c6ac514@nxp.com>
On Mon, Dec 11, 2017 at 10:57:41AM +0530, Hemant Agrawal wrote:
[...]
> > License text example in [1] starts from Copyright and has All rights
> > reserved.
> > I agree that template should be clearly specified from the very beginning.
> >
> > [1] https://spdx.org/licenses/BSD-3-Clause#licenseText
> >
> Hi all,
> Most templates are showing copyright first and SPDX later i.e. the typical
> way for writing the license.
>
> However some projects has followed it other way around to make it easy for
> tools i.e. the TOP line.
>
> I agree with Ferruh that we shall follow single convention. I will prefer
> to do it in following way to make it consistent. (I will also fix my change
> patches).
>
> >> Copyright (C) [YEAR] NAME-OF-COPYRIGHT-HOLDER
> >> Copyright (C) [YEAR] NAME-OF-COPYRIGHT-HOLDER-2
> >> Copyright (C) [YEAR] NAME-OF-COPYRIGHT-HOLDER-3
> >> SPDX-License-Identifier: BSD-3-Clause
OK for me, I'll send a v2.
Olivier
next prev parent reply other threads:[~2017-12-11 8:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 10:28 Olivier Matz
2017-12-08 17:29 ` Ferruh Yigit
2017-12-08 18:04 ` Stephen Hemminger
2017-12-08 18:22 ` Andrew Rybchenko
2017-12-11 5:27 ` Hemant Agrawal
2017-12-11 8:58 ` Olivier MATZ [this message]
2017-12-11 17:56 ` Ferruh Yigit
2017-12-12 16:57 ` Olivier MATZ
2017-12-13 5:13 ` Hemant Agrawal
2017-12-14 11:33 ` Hemant Agrawal
2017-12-14 12:58 ` Thomas Monjalon
2017-12-15 10:54 ` Hemant Agrawal
2017-12-22 15:59 ` [dpdk-dev] [PATCH v2] " Olivier Matz
2017-12-28 11:42 ` Hemant Agrawal
2018-01-05 10:32 ` Thomas Monjalon
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=20171211085851.4fefe3obd2g7bmbx@platinum \
--to=olivier.matz@6wind.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.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).