From: Joe Perches <joe@perches.com>
To: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linuxfoundation.org>,
Andrew Morton <akpm@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Kate Stewart <kate@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@lst.de>,
Russell King <rmk+kernel@armlinux.org.uk>,
Rob Herring <rob.herring@linaro.org>,
Jonas Oberg <jonas@fsfe.org>,
linux-xfs@vger.kernel.org,
Kate Stewart <kstewart@linuxfoundation.org>
Subject: Re: [patch 1/7] Documentation: Add license-rules.rst to describe how to properly identify file licenses
Date: Sun, 12 Nov 2017 11:54:34 -0800 [thread overview]
Message-ID: <1510516474.10883.59.camel@perches.com> (raw)
In-Reply-To: <20171112192142.525567667@linutronix.de>
On Sun, 2017-11-12 at 20:18 +0100, Thomas Gleixner wrote:
> Add a file to the Documentation directory to describe how file licenses
> should be described in all kernel files, using the SPDX identifier, as well
> as where all licenses should be in the kernel source tree for people to
> refer to (LICENSES/).
>
> Thanks to Kate, Philippe and Greg for review and editing!
p[
> --- /dev/null
> +++ b/Documentation/license-rules.rst
[]
> +The common way of expressing the license of a source file is to add the
> +matching boiler plate text into the top comment of the file. Due to
> +formatting, typos etc. These "boiler plates" are hard to validate for
> +tools, which are used in the context of license compliance.
There is bad sentence construction here and it is a
little difficult to parse what is intended.
"These" should not be capitalized.
This SPDX info should also be place in the Documentation/process
content somewhere.
next prev parent reply other threads:[~2017-11-12 20:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 19:18 [patch 0/7] LICENSES: Add documentation and initial License files Thomas Gleixner
2017-11-12 19:18 ` [patch 1/7] Documentation: Add license-rules.rst to describe how to properly identify file licenses Thomas Gleixner
2017-11-12 19:54 ` Joe Perches [this message]
2017-11-12 19:57 ` Thomas Gleixner
2017-11-12 20:07 ` Jonathan Corbet
2017-11-12 20:19 ` Thomas Gleixner
2017-11-13 10:04 ` [1/7] " Charlemagne Lasse
2017-11-13 12:26 ` Thomas Gleixner
2017-11-13 12:40 ` Charlemagne Lasse
2017-11-13 13:26 ` Thomas Gleixner
2017-11-16 15:07 ` [patch 1/7] " Jonathan Corbet
2017-11-16 15:15 ` Jonas Oberg
2017-11-16 18:03 ` Thomas Gleixner
2017-11-17 7:37 ` Philippe Ombredanne
2017-11-17 8:57 ` Greg Kroah-Hartman
2017-11-17 10:53 ` Philippe Ombredanne
2017-11-17 12:29 ` Greg Kroah-Hartman
2017-11-12 19:18 ` [patch 2/7] LICENSES: Add the GPL 2.0 license Thomas Gleixner
2017-11-14 18:02 ` Rob Herring
2017-11-14 19:05 ` Greg Kroah-Hartman
2017-11-16 11:46 ` Jonas Oberg
2017-11-16 13:12 ` Thomas Gleixner
2017-11-12 19:18 ` [patch 3/7] LICENSES: Add the GPL 1.0 license Thomas Gleixner
2017-11-12 19:18 ` [patch 4/7] LICENSES: Add the BSD 2-clause "Simplified" license Thomas Gleixner
2017-11-12 19:18 ` [patch 5/7] LICENSES: Add the BSD 3-clause "New" or "Revised" License Thomas Gleixner
2017-11-12 19:18 ` [patch 6/7] LICENSES: Add the MIT license Thomas Gleixner
2017-11-12 19:18 ` [patch 7/7] LICENSES: Add Linux syscall note exception Thomas Gleixner
2017-11-12 20:02 ` [patch 0/7] LICENSES: Add documentation and initial License files Joe Perches
2017-11-12 20:55 ` Thomas Gleixner
2017-11-13 13:54 ` Philippe Ombredanne
2017-11-14 10:15 ` Russell King - ARM Linux
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=1510516474.10883.59.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jonas@fsfe.org \
--cc=kate@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rob.herring@linaro.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linuxfoundation.org \
/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.