aboutsummaryrefslogtreecommitdiff
path: root/LICENSES
AgeCommit message (Collapse)AuthorFilesLines
2024-09-01LICENSES: add 0BSD license textLasse Collin1-0/+23
The license text was copied from: https://spdx.org/licenses/0BSD.html Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Lasse Collin <[email protected]> Reviewed-by: Sam James <[email protected]> Cc: Thomas Gleixner <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Cc: Albert Ou <[email protected]> Cc: Catalin Marinas <[email protected]> Cc: Emil Renner Berthing <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Joel Stanley <[email protected]> Cc: Jonathan Corbet <[email protected]> Cc: Jubin Zhong <[email protected]> Cc: Jules Maselbas <[email protected]> Cc: Krzysztof Kozlowski <[email protected]> Cc: Michael Ellerman <[email protected]> Cc: Palmer Dabbelt <[email protected]> Cc: Paul Walmsley <[email protected]> Cc: Randy Dunlap <[email protected]> Cc: Rui Li <[email protected]> Cc: Simon Glass <[email protected]> Cc: Will Deacon <[email protected]> Signed-off-by: Andrew Morton <[email protected]>
2022-11-08LICENSES: Add the copyleft-next-0.3.1 licenseLuis Chamberlain1-0/+236
Add the full text of the copyleft-next-0.3.1 license to the kernel tree as well as the required tags for reference and tooling. The license text was copied directly from the copyleft-next project's git tree [0]. Discussion of using copyleft-next-0.3.1 on Linux started since June, 2016 [1]. In the end Linus' preference was to have drivers use MODULE_LICENSE("GPL") to make it clear that the GPL applies when it comes to Linux [2]. Additionally, even though copyleft-next-0.3.1 has been found to be to be GPLv2 compatible by three attorneys at SUSE and Redhat [3], to err on the side of caution we simply recommend to always use the "OR" language for this license [4]. Even though it has been a goal of the project to be GPL-v2 compatible to be certain in 2016 I asked for a clarification about what makes copyleft-next GPLv2 compatible and also asked for a summary of benefits. This prompted some small minor changes to make compatibility even further clear and as of copyleft 0.3.1 compatibility should be crystal clear [5]. The summary of why copyleft-next 0.3.1 is compatible with GPLv2 is explained as follows: Like GPLv2, copyleft-next requires distribution of derivative works ("Derived Works" in copyleft-next 0.3.x) to be under the same license. Ordinarily this would make the two licenses incompatible. However, copyleft-next 0.3.1 says: "If the Derived Work includes material licensed under the GPL, You may instead license the Derived Work under the GPL." "GPL" is defined to include GPLv2. In practice this means copyleft-next code in Linux may be licensed under the GPL2, however there are additional obvious gains for bringing contributions from Linux outbound where copyleft-next is preferred. A summary of benefits why projects outside of Linux might prefer to use copyleft-next >= 0.3.1 over GPLv2: o It is much shorter and simpler o It has an explicit patent license grant, unlike GPLv2 o Its notice preservation conditions are clearer o More free software/open source licenses are compatible with it (via section 4) o The source code requirement triggered by binary distribution is much simpler in a procedural sense o Recipients potentially have a contract claim against distributors who are noncompliant with the source code requirement o There is a built-in inbound=outbound policy for upstream contributions (cf. Apache License 2.0 section 5) o There are disincentives to engage in the controversial practice of copyleft/ proprietary dual-licensing o In 15 years copyleft expires, which can be advantageous for legacy code o There are explicit disincentives to bringing patent infringement claims accusing the licensed work of infringement (see 10b) o There is a cure period for licensees who are not compliant with the license (there is no cure opportunity in GPLv2) o copyleft-next has a 'built-in or-later' provision The first driver submission to Linux under this dual strategy was lib/test_sysctl.c through commit 9308f2f9e7f05 ("test_sysctl: add dedicated proc sysctl test driver") merged in July 2017. Shortly after that I also added test_kmod through commit d9c6a72d6fa29 ("kmod: add test driver to stress test the module loader") in the same month. These two drivers went in just a few months before the SPDX license practice kicked in. In 2018 Kuno Woudt went through the process to get SPDX identifiers for copyleft-next [6] [7]. Although there are SPDX tags for copyleft-next-0.3.0, we only document use in Linux starting from copyleft-next-0.3.1 which makes GPLv2 compatibility crystal clear. This patch will let us update the two Linux selftest drivers in subsequent patches with their respective SPDX license identifiers and let us remove repetitive license boiler plate. [0] https://github.com/copyleft-next/copyleft-next/blob/master/Releases/copyleft-next-0.3.1 [1] https://lore.kernel.org/lkml/[email protected]/ [2] https://lore.kernel.org/lkml/CA+55aFyhxcvD+q7tp+-yrSFDKfR0mOHgyEAe=f_94aKLsOu0Og@mail.gmail.com/ [3] https://lore.kernel.org/lkml/[email protected]/ [4] https://lkml.kernel.org/r/[email protected] [5] https://lists.fedorahosted.org/archives/list/[email protected]/thread/JTGV56DDADWGKU7ZKTZA4DLXTGTLNJ57/#SQMDIKBRAVDOCT4UVNOOCRGBN2UJIKHZ [6] https://spdx.org/licenses/copyleft-next-0.3.0.html [7] https://spdx.org/licenses/copyleft-next-0.3.1.html Cc: Goldwyn Rodrigues <[email protected]> Cc: Kuno Woudt <[email protected]> Cc: Richard Fontana <[email protected]> Cc: [email protected] Cc: Ciaran Farrell <[email protected]> Cc: Christopher De Nicolo <[email protected]> Cc: Christoph Hellwig <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Cc: Thomas Gleixner <[email protected]> Cc: Jonathan Corbet <[email protected]> Cc: Thorsten Leemhuis <[email protected]> Cc: Andrew Morton <[email protected]> Reviewed-by: Kees Cook <[email protected]> Signed-off-by: Luis Chamberlain <[email protected]> Reviewed-by: Tim Bird <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
2021-12-16LICENSES/LGPL-2.1: Add LGPL-2.1-or-later as valid identifiersMauro Carvalho Chehab1-0/+2
Some files have been flagged with the new LGPL-2.1-or-later identifier which replace the original LGPL-2.1+ in the SPDX license identifier specification, but the identifiers are not mentioned as valid in the LGPL-2.1 license file. Add it, together with the LGPL-2.1-only at the the license file. Signed-off-by: Mauro Carvalho Chehab <[email protected]> Link: https://lore.kernel.org/r/12f38ebde4dcd8b1ecbd37df1b6ce2018426f6dd.1639657049.git.mchehab+huawei@kernel.org Signed-off-by: Greg Kroah-Hartman <[email protected]>
2021-07-15LICENSES/dual/CC-BY-4.0: Git rid of "smart quotes"Nishanth Menon1-1/+1
A couple of exotic quote characters came in with this license text; they can confuse software that is not expecting non-ASCII text. Switch to normal quotes here, with no changes to the actual license text. Reported-by: Rahul T R <[email protected]> Signed-off-by: Nishanth Menon <[email protected]> CC: Greg Kroah-Hartman <[email protected]> Acked-by: Thomas Gleixner <[email protected]> Acked-by: Thorsten Leemhuis <[email protected]> Acked-by: Randy Dunlap <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jonathan Corbet <[email protected]>
2020-12-08LICENSES: Add the CC-BY-4.0 licenseThorsten Leemhuis1-0/+410
Add the full text of the CC-BY-4.0 license to the kernel tree as well as the required tags for reference and tooling. The license text was copied directly from the following url, but for clarification a 'Creative Commons' was added before 'Attribution 4.0 International' in the first line: https://creativecommons.org/licenses/by/4.0/legalcode.txt CC-BY-4.0 is GPLv2 compatible, but when for example used for the kernel's documentation it can easily happen that sphinx during processing combines it with text or code from files using a more restrictive license[1]. This bears pitfalls, hence point that risk out and suggest to only use this license in combination with the GPLv2. [1] https://lkml.kernel.org/r/[email protected] Signed-off-by: Thorsten Leemhuis <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> CC: Thomas Gleixner <[email protected]> CC: Greg Kroah-Hartman <[email protected]> CC: Christoph Hellwig <[email protected]> Link: https://lore.kernel.org/r/7115b6c20ae3e6db0370fe4002dd586011205e1c.1607063223.git.linux@leemhuis.info Signed-off-by: Jonathan Corbet <[email protected]>
2020-09-16LICENSES/deprecated: add Zlib license textMikhail Zaslonko1-0/+27
The new files contributed to zlib have Zlib SPDX license identifier. Since there was no Zlib license text in LICENSES, scripts/spdxcheck.py reported the following errors: lib/zlib_dfltcc/dfltcc.c: 1:28 Invalid License ID: Zlib lib/zlib_dfltcc/dfltcc.h: 1:28 Invalid License ID: Zlib lib/zlib_dfltcc/dfltcc_deflate.c: 1:28 Invalid License ID: Zlib lib/zlib_dfltcc/dfltcc_inflate.c: 1:28 Invalid License ID: Zlib lib/zlib_dfltcc/dfltcc_util.h: 1:28 Invalid License ID: Zlib The patch adds Zlib SPDX license to LICENSES/deprecated, thus resolving the issues reported by spdxcheck. Suggested-by: Lukas Bulwahn <[email protected]> Reviewed-by: Lukas Bulwahn <[email protected]> Signed-off-by: Mikhail Zaslonko <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
2020-09-16LICENSE: add GFDL deprecated licensesMauro Carvalho Chehab2-0/+794
There are some files under Documentation which uses deprecated versions of GNU Free Documentation License, on both versions 1.1 and 1.2. On all cases, the license is with no Invariant Sections, Front-Cover Texts or Back-Cover Texts. Add the text file for them, as we'll start using SPDX for those. Signed-off-by: Mauro Carvalho Chehab <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
2019-05-03LICENSES: Rename other to deprecatedChristoph Hellwig4-0/+0
Make it clear in the directory name that these are not intended for new code. Signed-off-by: Christoph Hellwig <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2019-05-03LICENSES: Clearly mark dual license only licensesChristoph Hellwig3-2/+10
Just like the CDDL the Apache license and the MPL must only be used as a choice in additional to an GPL2 compatible license. Copy over the boilerplate from the CDDL file to the other two after fixing it up to make it clear the licenses need to be GPL2 compatible, not just the more generic GPL compatible. For example the Apache 2 license is GPL3 compatible, but that doesn't matter for the kernel. Also move these licenses to a separate directory and document the rules in license-rules.rst. Signed-off-by: Christoph Hellwig <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2019-01-16LICENSES: Add GCC runtime library exception textThomas Gleixner1-0/+18
A recent commit added SPDX identifiers to the SuperH low level library code which originates from GCC. This code is licensed under the GPL 2.0 or later with the GCC runtime library exception. Unfortunately the authors did not bother to add the exception text to the LICENSES directory so spdxcheck fails with: arch/sh/lib/ashiftrt.S: 1:42 Invalid Exception ID: GCC-exception-2.0 arch/sh/lib/ashlsi3.S: 1:42 Invalid Exception ID: GCC-exception-2.0 arch/sh/lib/ashrsi3.S: 1:42 Invalid Exception ID: GCC-exception-2.0 arch/sh/lib/lshrsi3.S: 1:42 Invalid Exception ID: GCC-exception-2.0 arch/sh/lib/movmem.S: 1:42 Invalid Exception ID: GCC-exception-2.0 arch/sh/lib/udiv_qrnnd.S: 1:42 Invalid Exception ID: GCC-exception-2.0 arch/sh/lib/udivsi3.S: 1:42 Invalid Exception ID: GCC-exception-2.0 arch/sh/lib/udivsi3_i4i-Os.S: 1:42 Invalid Exception ID: GCC-exception-2.0 arch/sh/lib/udivsi3_i4i.S: 1:42 Invalid Exception ID: GCC-exception-2.0 Add the exception text along with the required tags which allow automated checking. Fixes: 4494ce4fb4ff ("sh: lib: convert to SPDX identifiers") Signed-off-by: Thomas Gleixner <[email protected]> Acked-by: Greg Kroah-Hartman <[email protected]> Cc: Kuninori Morimoto <[email protected]> Cc: Simon Horman <[email protected]> Cc: Yoshinori Sato <[email protected]> Cc: Rich Felker <[email protected]> Cc: Andrew Morton <[email protected]> Cc: Kate Stewart <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-10-24Merge tag 'docs-4.20' of git://git.lwn.net/linuxLinus Torvalds2-1/+29
Pull documentation updates from Jonathan Corbet: "This is a fairly typical cycle for documentation. There's some welcome readability improvements for the formatted output, some LICENSES updates including the addition of the ISC license, the removal of the unloved and unmaintained 00-INDEX files, the deprecated APIs document from Kees, more MM docs from Mike Rapoport, and the usual pile of typo fixes and corrections" * tag 'docs-4.20' of git://git.lwn.net/linux: (41 commits) docs: Fix typos in histogram.rst docs: Introduce deprecated APIs list kernel-doc: fix declaration type determination doc: fix a typo in adding-syscalls.rst docs/admin-guide: memory-hotplug: remove table of contents doc: printk-formats: Remove bogus kobject references for device nodes Documentation: preempt-locking: Use better example dm flakey: Document "error_writes" feature docs/completion.txt: Fix a couple of punctuation nits LICENSES: Add ISC license text LICENSES: Add note to CDDL-1.0 license that it should not be used docs/core-api: memory-hotplug: add some details about locking internals docs/core-api: rename memory-hotplug-notifier to memory-hotplug docs: improve readability for people with poorer eyesight yama: clarify ptrace_scope=2 in Yama documentation docs/vm: split memory hotplug notifier description to Documentation/core-api docs: move memory hotplug description into admin-guide/mm doc: Fix acronym "FEKEK" in ecryptfs docs: fix some broken documentation references iommu: Fix passthrough option documentation ...
2018-10-18LICENSES: Remove CC-BY-SA-4.0 license textChristoph Hellwig1-397/+0
Using non-GPL licenses for our documentation is rather problematic, as it can directly include other files, which generally are GPLv2 licensed and thus not compatible. Remove this license now that the only user (idr.rst) is gone to avoid people semi-accidentally using it again. Signed-off-by: Christoph Hellwig <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
2018-10-12LICENSES: Add ISC license textHans de Goede1-0/+24
Add the full text of the ISC license to the kernel tree. It was copied directly from: https://spdx.org/licenses/ISC.html With the mention of "ISC" in the warranty disclaimer replaced with "THE AUTHOR" as done in the ISC license headers used in the ath10k and brcmfmac wifi drivers. Cc: Kalle Valo <[email protected]> Signed-off-by: Hans de Goede <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-10-12LICENSES: Add note to CDDL-1.0 license that it should not be usedHans de Goede1-1/+5
The only reason we have the CDDL-1.0 license text around is for some dual-licensed files from virtualbox. New code should not use this license. Add a note about this and change the example tag to be dual-licensed. Signed-off-by: Hans de Goede <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-04-27LICENSES: Add Linux-OpenIB license textThomas Gleixner1-0/+26
The infiniband code uses a variant of the OpenIB license. This license is BSD-2-Clause with the MIT disclaimer. The linux kernel uses this license extensively throughout the driver subsystem since 2005. Note that the OpenIB.org license is a true match to BSD-2-Clause. The license text was copied from: https://spdx.org/licenses/Linux-OpenIB.html#licenseText Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-04-27LICENSES: Add CC-BY-SA-4.0 license textThomas Gleixner1-0/+397
Add the full text of the CC-BY-SA-4.0 license to the kernel tree. It was copied directly from: https://spdx.org/licenses/CC-BY-SA-4.0.html#licenseText Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-04-27LICENSES: Add CDDL-1.0 license textThomas Gleixner1-0/+364
Add the full text of the CDDL-1.0 to the kernel tree. It was copied directly from: https://spdx.org/licenses/CDDL-1.0.html#licenseText Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-04-27LICENSES: Add Apache 2.0 license textThomas Gleixner1-0/+183
Add the full text of the Apache License version 2 to the kernel tree. It was copied directly from: https://spdx.org/licenses/Apache-2.0.html#licenseText Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-04-27LICENSES: Add X11 licenseThomas Gleixner1-0/+37
Add the full text of the X11 to the kernel tree. It was copied directly from: https://spdx.org/licenses/X11.html#licenseText Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-04-27LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiersThomas Gleixner2-1/+7
Quite some files have been flagged with the new GPL-2.0-only and GPL-2.0-or-later identifiers which replace the original GPL-2.0 and GPL-2.0+ identifiers in the SPDX license identifier specification, but the identifiers are not mentioned as valid in the GPL-2.0 license file. Add them to the license file and to the Linux-syscall-note exception to make everything consistent again. Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Reviewed-by: Mauro Carvalho Chehab <[email protected]> Cc: Hans Verkuil <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-01-06LICENSES: Add MPL-1.1 licenseThomas Gleixner1-0/+478
Add the full text of the Mozilla Public License 1.1 to the kernel tree. It was copied directly from: https://spdx.org/licenses/MPL-1.1.html#licenseText Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Philippe Ombredanne <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-01-06LICENSES: Add the GPL 1.0 licenseThomas Gleixner1-0/+260
Add the full text of the GPL 1.0 license to the kernel tree. It was copied directly from: https://spdx.org/licenses/GPL-1.0.html#licenseText Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Philippe Ombredanne <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-01-06LICENSES: Add Linux syscall note exceptionThomas Gleixner1-0/+25
Copied from the Linux kernel COPYING file. Add the required tags for reference and tooling. Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Philippe Ombredanne <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-01-06LICENSES: Add the MIT licenseThomas Gleixner1-0/+30
Add the full text of the MIT license to the kernel tree. It was copied directly from: https://spdx.org/licenses/MIT.html#licenseText Add the required tags for reference and tooling. Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Philippe Ombredanne <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-01-06LICENSES: Add the BSD-3-clause "Clear" licenseThomas Gleixner1-0/+41
Add the full text of the BSD 3-clause "Clear" License to the kernel tree. It was copied directly from: https://spdx.org/licenses/BSD-3-Clause-Clear.html Add the required tags for reference and tooling. Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Philippe Ombredanne <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-01-06LICENSES: Add the BSD 3-clause "New" or "Revised" LicenseThomas Gleixner1-0/+36
Add the full text of the BSD 3-clause "New" or "Revised" License to the kernel tree. It was copied directly from: https://spdx.org/licenses/BSD-3-Clause.html#licenseText Add the required tags for reference and tooling. Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Philippe Ombredanne <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-01-06LICENSES: Add the BSD 2-clause "Simplified" licenseThomas Gleixner1-0/+32
Add the full text of the BSD 2-clause "Simplified" license to the kernel tree. It was copied directly from: https://spdx.org/licenses/BSD-2-Clause.html#licenseText Add the required tags for reference and tooling. Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Philippe Ombredanne <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-01-06LICENSES: Add the LGPL-2.1 licenseThomas Gleixner1-0/+503
Add the full text of the LGPL 2.1 license to the kernel tree. It was copied directly from: https://spdx.org/licenses/LGPL-2.1.html#licenseText Add the required tags for reference and tooling. Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Philippe Ombredanne <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-01-06LICENSES: Add the LGPL 2.0 licenseThomas Gleixner1-0/+487
Add the full text of the LGPL 2.0 license to the kernel tree. It was copied directly from: https://spdx.org/licenses/LGPL-2.0.html#licenseText Add the required tags for reference and tooling. Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Philippe Ombredanne <[email protected]> Reviewed-by: Kate Stewart <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
2018-01-06LICENSES: Add the GPL 2.0 licenseThomas Gleixner1-0/+353
Add the full text of the GPL 2.0 license to the LICENSES directory. It was copied directly from the COPYING file in the kernel source tree as it differs from the public available version of the license in various places including the FSF. Philippe did some research on the GPL2.0 history: There is NO trustworthy version of an official GPL 2.0 text: the FSF official texts are all fubar (if only in small and subtle ways). The FSF texts should be authoritative, but then which one? They published more GPL 2.0 versions than most. So we would be hard pressed to blame SPDX or the OSI for having their own minor variant. Then in digging further, I found the ONE true original GPL with a file time stamp on June 2 1991, 01:50 (AM?, PM? unknown time zone?) ! in an old GCC archive. For the posterity and everyone's enjoyment I have built a git history of GPL 2.0 Mark1 to Mark6 See https://github.com/pombredanne/gpl-history/commits/master/COPYING I also added a shorter history of the Linux COPYING text. The first version in Linus's git tree is based on the very fine and well tuned GPL 2 Mark4, the first fully Y2K compliant version of the GPL 2, as you can see from the diffs with the former Mark3: that was dangerously stuck in the last century. The current version in is based on a rare GPL 2.0 Mark5.1 aka "Franklin St", that I do not have in my history yet and spells "Franklin St." rather than "Franklin Street." Therefore there is likely another GPL 2.0 version between Mark4 and Mark5 that I have yet to find and may not have been caught by the archive.org spiders. Here help and patches welcomed: this is likely an important missing link. Further information about this archaelogical research; http://lkml.kernel.org/r/CAOFm3uEzRMf261+O-Nm+9HDoEn9RbFjH=5J9i1C2GgMUg2G4LA@mail.gmail.com Add the required tags for reference and tooling. Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Reviewed-by: Philippe Ombredanne <[email protected]> Reviewed-by: Jonas Oberg <[email protected]> Reviewed-by: Darrick J. Wong <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>