From: Arend van Spriel <arend@broadcom.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Joe Perches <joe@perches.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>,
Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [net] nfc: Fix FSF address in file headers
Date: Sun, 8 Dec 2013 17:17:47 +0100 [thread overview]
Message-ID: <52A49BAB.1050805@broadcom.com> (raw)
In-Reply-To: <1386457281.2195.55.camel@jtkirshe-mobl>
On 12/08/2013 12:01 AM, Jeff Kirsher wrote:
> On Sat, 2013-12-07 at 14:55 -0800, Joe Perches wrote:
>> On Sat, 2013-12-07 at 14:49 -0800, Jeff Kirsher wrote:
>>> On Sat, 2013-12-07 at 23:20 +0100, Arend van Spriel wrote:
>>>> On 12/06/2013 05:56 PM, Jeff Kirsher wrote:
>>>>> Several files refer to an old address for the Free Software Foundation
>>>>> in the file header comment. Resolve by replacing the address with
>>>>> the URL<http://www.gnu.org/licenses/> so that we do not have to keep
>>>>> updating the header comments anytime the address changes.
>>>>
>>>> This seems to pop up from time to time and unfortunately the resolution
>>>> seems not consistent at those times. Why not simply refer to the full
>>>> license text that is in the COPYING file in the tree itself.
>>>
>>> I, personally have only had one request in the last 10 years to change
>>> our Intel Wired Ethernet headers and that was because the address
>>> changed. I am open to suggestions, although when I proposed either
>>> updating the address to the current address or use the URL on LKML and
>>> netdev, the response I got was to update to the use the URL.
>>>
>>> I guess the only argument I would have against referring to the COPYING
>>> in the tree itself is that the headers already state:
>>>
>>> You should have received a copy of the GNU General Public License along
>>> with this program;
>>>
>>> (which refers to the COPYING file) and then it states...
>>>
>>> if not, write to the Free Software Foundation, Inc.,
>>> 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
>>>
>>> This is the second part that needs cleanup if the file refers to the old
>>> address. So just by removing the address and providing the URL, you are
>>> providing a place that users can get the license *if* the COPYING file
>>> gets removed (or altered) by who ever releases the kernel.
>>
>> Hi Jeff.
>>
>> I think what you've done is fine, but remember that
>> URLs come and go too.
>
> True, I just wish that were true for those embarrassing pictures of me
> 20 years ago... <joking>
Hmmm. Nothing on google. Probably the NSA already removed it for you
(yikes, did that got me blacklisted).
Gr. AvS
>>
>> There was a discussion about this just a bit ago on lkml
>> https://lkml.org/lkml/2013/10/6/158
>> and this message was added to checkpatch recently:
>>
>> "Do not include the paragraph about writing to the Free Software
>> Foundation's mailing address from the sample GPL notice. The FSF has
>> changed addresses in the past, and may do so again. Linux already
>> includes a copy of the GPL.\n"
>
> Thanks for the info, I overlooked that thread.
>
>
prev parent reply other threads:[~2013-12-08 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 16:56 [net] nfc: Fix FSF address in file headers Jeff Kirsher
2013-12-07 22:20 ` Arend van Spriel
2013-12-07 22:49 ` Jeff Kirsher
2013-12-07 22:55 ` Joe Perches
2013-12-07 23:01 ` Jeff Kirsher
2013-12-08 16:17 ` Arend van Spriel [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=52A49BAB.1050805@broadcom.com \
--to=arend@broadcom.com \
--cc=aloisio.almeida@openbossa.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=joe@perches.com \
--cc=lauro.venancio@openbossa.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sameo@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.