Skip to content

Commit 4764b2f

Browse files
authored
COYPING: restore the full text text of GPL (ethereum#21568)
When the license was added to the repository, its text was changed (some sections at the end removed) and, worse, the authors of go-ethereum tried to claim copyright on the license text. The correct way to apply GPL to a project is to copy it verbatim. This change reverts the text of the GPL to the original.
1 parent b65c384 commit 4764b2f

File tree

1 file changed

+57
-2
lines changed

1 file changed

+57
-2
lines changed

COPYING

+57-2
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
GNU GENERAL PUBLIC LICENSE
22
Version 3, 29 June 2007
33

4-
Copyright (C) 2014 The go-ethereum Authors.
4+
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
55
Everyone is permitted to copy and distribute verbatim copies
66
of this license document, but changing it is not allowed.
77

@@ -616,4 +616,59 @@ above cannot be given local legal effect according to their terms,
616616
reviewing courts shall apply local law that most closely approximates
617617
an absolute waiver of all civil liability in connection with the
618618
Program, unless a warranty or assumption of liability accompanies a
619-
copy of the Program in return for a fee.
619+
copy of the Program in return for a fee.
620+
621+
END OF TERMS AND CONDITIONS
622+
623+
How to Apply These Terms to Your New Programs
624+
625+
If you develop a new program, and you want it to be of the greatest
626+
possible use to the public, the best way to achieve this is to make it
627+
free software which everyone can redistribute and change under these terms.
628+
629+
To do so, attach the following notices to the program. It is safest
630+
to attach them to the start of each source file to most effectively
631+
state the exclusion of warranty; and each file should have at least
632+
the "copyright" line and a pointer to where the full notice is found.
633+
634+
<one line to give the program's name and a brief idea of what it does.>
635+
Copyright (C) <year> <name of author>
636+
637+
This program is free software: you can redistribute it and/or modify
638+
it under the terms of the GNU General Public License as published by
639+
the Free Software Foundation, either version 3 of the License, or
640+
(at your option) any later version.
641+
642+
This program is distributed in the hope that it will be useful,
643+
but WITHOUT ANY WARRANTY; without even the implied warranty of
644+
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
645+
GNU General Public License for more details.
646+
647+
You should have received a copy of the GNU General Public License
648+
along with this program. If not, see <https://www.gnu.org/licenses/>.
649+
650+
Also add information on how to contact you by electronic and paper mail.
651+
652+
If the program does terminal interaction, make it output a short
653+
notice like this when it starts in an interactive mode:
654+
655+
<program> Copyright (C) <year> <name of author>
656+
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
657+
This is free software, and you are welcome to redistribute it
658+
under certain conditions; type `show c' for details.
659+
660+
The hypothetical commands `show w' and `show c' should show the appropriate
661+
parts of the General Public License. Of course, your program's commands
662+
might be different; for a GUI interface, you would use an "about box".
663+
664+
You should also get your employer (if you work as a programmer) or school,
665+
if any, to sign a "copyright disclaimer" for the program, if necessary.
666+
For more information on this, and how to apply and follow the GNU GPL, see
667+
<https://www.gnu.org/licenses/>.
668+
669+
The GNU General Public License does not permit incorporating your program
670+
into proprietary programs. If your program is a subroutine library, you
671+
may consider it more useful to permit linking proprietary applications with
672+
the library. If this is what you want to do, use the GNU Lesser General
673+
Public License instead of this License. But first, please read
674+
<https://www.gnu.org/licenses/why-not-lgpl.html>.

0 commit comments

Comments
 (0)