[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOFm3uHr8Vi5dG054qzPmvkD1=urZy+u2pr0sRruBBXgRunkeA@mail.gmail.com>
Date: Thu, 4 Jan 2018 21:50:05 +0100
From: Philippe Ombredanne <pombredanne@...b.com>
To: Carmen Bianca Bakker <carmenbianca@...e.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...uxfoundation.org>,
Andrew Morton <akpm@...uxfoundation.org>,
Jonathan Corbet <corbet@....net>,
Kate Stewart <kstewart@...uxfoundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Christoph Hellwig <hch@....de>,
Russell King <rmk+kernel@...linux.org.uk>,
Rob Herring <rob.herring@...aro.org>,
Jonas Oberg <jonas@...e.org>, Joe Perches <joe@...ches.com>,
xfs <linux-xfs@...r.kernel.org>,
Charlemagne Lasse <charlemagnelasse@...il.com>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [patch V5 02/11] LICENSES: Add the GPL 2.0 license
Carmen,
On Thu, Jan 4, 2018 at 5:25 PM, Carmen Bianca Bakker
<carmenbianca@...e.org> wrote:
> Hi all,
>
> Since December, `GPL-2.0` is no longer the correct identifier for the
> licence. The American FSF has been in talks with the SPDX Workgroup to
> change it to `GPL-2.0-only`.
>
> See the rationale here:
>
> https://www.gnu.org/licenses/identify-licenses-clearly.html
>
> See the new canonical licence list here:
>
> https://spdx.org/licenses/
>
> This change is valid for all GPL licences. Similarly, `GPL-2.0+` has
> been changed to `GPL-2.0-or-later`.
This is exactly to insulate against these kinds of changes that this
doc patch exists in the first place and documents what things mean for
the kernel.
> I believe that this patch should be changed to reflect that. The
> identifiers used in this patch are still valid, but deprecated.
Kernel-wise I do not think we can be assume that changes such as these
could be implemented right away so there is no need to change the doc
at this stage.
For now the kernel doc is the reference and nothing else. So this
patch should NOT be changed IMHO at least not now.
Eventually this could happen in the future, but not out of order with
actual patches to update the code and tooling and certainly not now.
--
Cordially
Philippe Ombredanne
Powered by blists - more mailing lists