[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180322121355.GA16195@bombadil.infradead.org>
Date: Thu, 22 Mar 2018 05:13:55 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Mauro Carvalho Chehab <mchehab@...pensource.com>
Cc: Jonathan Corbet <corbet@....net>,
LKML <linux-kernel@...r.kernel.org>,
Linux-doc <linux-doc@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Jonas Oberg <jonas@...e.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Philippe Ombredanne <pombredanne@...b.com>,
Kate Stewart <kstewart@...uxfoundation.org>
Subject: Re: [PATCH 1/2] COPYING: create a new file with points to the Kernel
license files
On Thu, Mar 22, 2018 at 06:54:13AM -0300, Mauro Carvalho Chehab wrote:
> +++ b/Documentation/process/license-rules.rst
> @@ -4,15 +4,17 @@ Linux kernel licensing rules
> ============================
>
> The Linux Kernel is provided under the terms of the GNU General Public
> -License version 2 only (GPL-2.0), as published by the Free Software
> -Foundation, and provided in the COPYING file. This documentation file is
> -not meant to replace the COPYING file, but provides a description of how
> -each source file should be annotated to make the licensing it is governed
> -under clear and unambiguous.
> -
> -The license in the COPYING file applies to the kernel source as a whole,
> -though individual source files can have a different license which is
> -required to be compatible with the GPL-2.0::
> +version 2 only (GPL-2.0), as written at LICENSES/preferred/GPL-2.0,
^^^ you dropped the word 'License' here
Also, I think this should read "as provided in", not "as written at".
> +with an explicit syscall exception described at
s/at/in/
> +LICENSES/exceptions/Linux-syscall-note, as described in the COPYING file.
This phrasing is awkward with "desribed" used twice in the same sentence ...
> +This documentation file is not meant to replace the Kernel's license,
> +but provides a description of how each source file should be annotated
> +to make the licensing it is governed under clear and unambiguous.
I'd rather this said:
This documentation file provides a description of how each source file
should be annotated to make its license clear and unambiguous.
Powered by blists - more mailing lists