From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] remove redundant file header note
Date: Wed, 23 Aug 2017 22:40:50 +0200 [thread overview]
Message-ID: <3084352.EgKNohe7Fy@xps> (raw)
In-Reply-To: <20170821135103.22631-1-ferruh.yigit@intel.com>
21/08/2017 15:51, Ferruh Yigit:
> Some of the "All rights reserved." note looks like duplicate, there is
> one for each copyright note in the same line, and extra one after the
> copyright notes. Sample is in below patch.
>
> Although this looks like a duplication, I am not sure if this is a legal
> requirement, or legally has a meaning.
I think the whole sentence "All rights reserved" has no meaning
and could be removed in both lines, but I am not a lawyer :)
I'm afraid lawyers won't take the risk to change these lines.
[...]
> # Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
> -# All rights reserved.
You could also remove "(c)" after Copyright.
next prev parent reply other threads:[~2017-08-23 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 13:51 Ferruh Yigit
2017-08-23 20:40 ` Thomas Monjalon [this message]
2017-08-24 14:05 ` Ferruh Yigit
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=3084352.EgKNohe7Fy@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).