From: Joe Perches <joe@perches.com>
To: Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Philippe Ombredanne <pombredanne@nexb.com>,
Christoph Hellwig <hch@infradead.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Eric Sandeen <sandeen@redhat.com>,
xfs <linux-xfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Kate Stewart <kstewart@linuxfoundation.org>
Subject: Re: WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Date: Sat, 25 Nov 2017 13:57:33 -0800 [thread overview]
Message-ID: <1511647053.2503.22.camel@perches.com> (raw)
In-Reply-To: <20171125191223.GC5114@amd>
On Sat, 2017-11-25 at 20:12 +0100, Pavel Machek wrote:
> [Linus Torvalds...]
> > Having it be the first line of the file is good, it's obvious, and
> > stands out, which is the point, you want it to, it's a license :)
>
> What is good about that? License is about the least interesting thing
> about the file. Point of SPDX conversion (see the mail I was replying
> to?) was to make license information _less_ intrusive, not more. Tools
> can find SPDX anywhere in the file for the people that really care.
>
> That's how it works in U-Boot, which people are using as example of
> reasonable SPDX conversion:
>
> /*
> * Copyright (c) 2012 The Chromium OS Authors. All rights reserved.
> * Copyright (c) 2010-2011 NVIDIA Corporation
> * NVIDIA Corporation <www.nvidia.com>
> *
> * SPDX-License-ers/ d
> .c: GPL-2.0+
> */
fwiw: I agree with Pavel.
My preferred header listing order:
// Simple description/purpose
// Copyright/Author
// License
next prev parent reply other threads:[~2017-11-25 21:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171107020607.GA26910@magnolia>
2017-11-07 7:20 ` WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license Christoph Hellwig
2017-11-07 7:39 ` Greg Kroah-Hartman
2017-11-07 17:07 ` Alan Cox
2017-11-07 17:12 ` Greg Kroah-Hartman
2017-11-07 17:25 ` Alan Cox
2017-11-07 18:30 ` Greg Kroah-Hartman
2017-11-07 17:20 ` Darrick J. Wong
2017-11-07 18:29 ` Greg Kroah-Hartman
2017-11-07 18:46 ` Alan Cox
2017-11-07 19:15 ` Theodore Ts'o
2017-11-07 19:28 ` Christoph Hellwig
2017-11-07 20:26 ` Greg Kroah-Hartman
2017-11-07 21:42 ` Luis R. Rodriguez
2017-11-08 6:37 ` Greg Kroah-Hartman
2017-11-08 17:19 ` Alan Cox
2017-11-08 18:46 ` Darrick J. Wong
2017-11-09 8:19 ` Greg Kroah-Hartman
2017-11-08 12:35 ` Philippe Ombredanne
2017-11-08 15:11 ` Christoph Hellwig
2017-11-08 18:06 ` Christoph Hellwig
2017-11-09 8:23 ` Greg Kroah-Hartman
2017-11-09 8:53 ` Christoph Hellwig
2017-11-22 17:07 ` Pavel Machek
2017-11-22 17:53 ` Greg Kroah-Hartman
2017-11-25 19:12 ` Pavel Machek
2017-11-25 21:57 ` Joe Perches [this message]
2017-11-27 16:50 ` Darrick J. Wong
2017-11-22 16:19 ` Pavel Machek
2017-11-08 23:47 ` Dave Chinner
2017-11-09 8:16 ` Greg Kroah-Hartman
2017-11-10 21:10 ` Alan Cox
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=1511647053.2503.22.camel@perches.com \
--to=joe@perches.com \
--cc=darrick.wong@oracle.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=pombredanne@nexb.com \
--cc=sandeen@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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