git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2 3/5] COPYING: remove mention of GPLv3, clarify sub-project COPYING

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Oct 5, 2021, 17:01 UTC
Message-ID
<patch-v2-3.5-44375bece46-20211005T170031Z-avarab@gmail.com>
In-Reply-To
<cover-v2-0.5-00000000000-20211005T170031Z-avarab@gmail.com>

The COPYING file added in [1] is a product of its era, at the time discussions around the GPLv3 were quite active. Since then we have had almost no "GPL v2 or later" notices anywhere.

Since then[2][3] linux.git has replaced its version of almost the identical wording with something that's a bit more formal, and which isn't mostly addressing a hypothetical future GPL v3 migration. Let's do the same. Now we:

A. Let it suffice to say that things are licensed under GPL v2 unless
   explicitly otherwise stated. The new wording is an amalgamation of
   the start of Linux's "COPYING" file[4] and the end of our pre-image
   first paragraph added in[1].
B. Add some brief wording about how the licenses of subdirectories
   such as "sha1dc/" and "compat/regex/" should be discovered. This is
   also intended to cover future in-tree additions such as the
   "reftable" directory[5][6].
C. Include the same "subject to this COPYING file" wording as
   linux.git has used since[7].
1. 075b845a857 (Add a COPYING notice, making it explicit that the
   license is GPLv2., 2005-04-11)
2. torvalds/linux@bf02d491237e (COPYING: use the new text with points
   to the license files, 2018-03-23)
3. torvalds/linux@74835c7db032 (COPYING: state that all contributions
   really are covered by this file, 2020-02-06)
4. torvalds/linux@88de995ccf48 (COPYING: create a new file with points
   to the Kernel license files, 2018-03-23)
5. https://lore.kernel.org/git/2597ddfeae1d9da8695151f62379c85621ad0fcb.1632841817.git.gitgitgadget@gmail.com/
6. https://lore.kernel.org/git/xmqqtui4k1j5.fsf@gitster.g/
7. torvalds/linux@74835c7db032 (COPYING: state that all contributions
   really are covered by this file, 2020-02-06)
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
---
 COPYING | 35 +++++++++++++++++------------------
 1 file changed, 17 insertions(+), 18 deletions(-)
diff --git a/COPYING b/COPYING
index 536e55524db..19de8f2ea1b 100644
--- a/COPYING
+++ b/COPYING
@@ -1,21 +1,20 @@
-
- Note that the only valid version of the GPL as far as this project
- is concerned is _this_ particular version of the license (ie v2, not
- v2.2 or v3.x or whatever), unless explicitly otherwise stated.
-
- HOWEVER, in order to allow a migration to GPLv3 if that seems like
- a good idea, I also ask that people involved with the project make
- their preferences known. In particular, if you trust me to make that
- decision, you might note so in your copyright message, ie something
- like
-
-	This file is licensed under the GPL v2, or a later version
-	at the discretion of Linus.
-
-  might avoid issues. But we can also just decide to synchronize and
-  contact all copyright holders on record if/when the occasion arises.
-
-			Linus Torvalds
+Git is provided under the terms of the GNU General Public License
+version 2 only (GPL-2.0), unless explicitly otherwise stated.
+
+The license described in this COPYING file applies to Git's source as
+a whole, though individual source files can have a different license
+which is required to be compatible with the GPL-2.0. All contributions
+to Git are subject to this COPYING file.
+
+Different but compatible licenses may apply to individual files or
+directories. Defer to files matching "*COPYING*" or "*LICENSE*" in
+subdirectories for the license of files therein, or to copyright
+notices at the top of individual files.
+
+Examples include "sha1dc/LICENSE.txt" covering the imported "sha1dc/"
+directory (and optional "sha1collisiondetection/" submodule), the
+"xdiff/" directory licensed under the LGPL v2.1 (see the "LGPL-2.1"
+file), and imported external code such as "compat/regex/".
 
 ----------------------------------------
 
-- 
2.33.0.1441.gbbcdb4c3c66
Previous: Ævar Arnfjörð BjarmasonNext: Ævar Arnfjörð Bjarmason
Message 14 of 20 in “COPYING: modernize, steal boilerplate from linux.git”
  1. 0/5 COPYING: modernize, steal boilerplate from linux.gitÆvar Arnfjörð Bjarmason, Oct 2, 2021
  2. 1/5 "lib-diff" tests: make "README" and "COPYING" test data smallerÆvar Arnfjörð Bjarmason, Oct 2, 2021
  3. Han-Wen NienhuysOct 4, 2021
  4. Ævar Arnfjörð BjarmasonOct 4, 2021
  5. 2/5 tests: stop using top-level "README" and "COPYING" filesÆvar Arnfjörð Bjarmason, Oct 2, 2021
  6. 3/5 COPYING: remove mention of GPLv3, clarify sub-project COPYINGÆvar Arnfjörð Bjarmason, Oct 2, 2021
  7. Junio C HamanoOct 4, 2021
  8. 5/5 GPL-2.0: update to byte-for-byte match the FSF's versionÆvar Arnfjörð Bjarmason, Oct 2, 2021
  9. 4/5 COPYING: move GPL text to a "GPL-2.0" fileÆvar Arnfjörð Bjarmason, Oct 2, 2021
  10. Han-Wen NienhuysOct 4, 2021
  11. 0/5 COPYING: modernize, steal boilerplate from linux.gitÆvar Arnfjörð Bjarmason, Oct 5, 2021
  12. 2/5 tests: stop using top-level "README" and "COPYING" filesÆvar Arnfjörð Bjarmason, Oct 5, 2021
  13. 1/5 "lib-diff" tests: make "README" and "COPYING" test data smallerÆvar Arnfjörð Bjarmason, Oct 5, 2021
  14. 3/5 COPYING: remove mention of GPLv3, clarify sub-project COPYINGÆvar Arnfjörð Bjarmason, Oct 5, 2021
  15. 5/5 GPL-2.0: update to byte-for-byte match the FSF's versionÆvar Arnfjörð Bjarmason, Oct 5, 2021
  16. 4/5 COPYING: move GPL text to a "GPL-2.0" fileÆvar Arnfjörð Bjarmason, Oct 5, 2021
  17. 0/2 tests: stop relying on top-level COPYING and READMEÆvar Arnfjörð Bjarmason, Oct 15, 2021
  18. 2/2 tests: stop using top-level "README" and "COPYING" filesÆvar Arnfjörð Bjarmason, Oct 15, 2021
  19. 1/2 "lib-diff" tests: make "README" and "COPYING" test data smallerÆvar Arnfjörð Bjarmason, Oct 15, 2021
  20. Junio C HamanoOct 15, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.