From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] remove redundant file header note
Date: Thu, 24 Aug 2017 15:05:38 +0100 [thread overview]
Message-ID: <f0daa993-482b-b123-3814-198836cafc54@intel.com> (raw)
In-Reply-To: <3084352.EgKNohe7Fy@xps>
On 8/23/2017 9:40 PM, Thomas Monjalon wrote:
> 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.
I also don't dare to take that risk :)
Let me send a patch just to remove standalone "All rights reserved." lines..
>
> [...]
>> # Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
>> -# All rights reserved.
>
> You could also remove "(c)" after Copyright.
>
prev parent reply other threads:[~2017-08-24 14:06 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
2017-08-24 14:05 ` Ferruh Yigit [this message]
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=f0daa993-482b-b123-3814-198836cafc54@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@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).