From: ams@gnu.org (Alfred M. Szmidt)
To: Joel Brobecker <brobecker@adacore.com>
Cc: mark.kettenis@xs4all.nl, gdb-patches@sourceware.org
Subject: Re: Update some sim copyright headers to GPLv3-or-later
Date: Thu, 20 Dec 2012 18:20:00 -0000 [thread overview]
Message-ID: <E1Tlkj6-0008TE-12@fencepost.gnu.org> (raw)
In-Reply-To: <20121219090457.GT3273@adacore.com> (message from Joel Brobecker on Wed, 19 Dec 2012 13:04:58 +0400)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2807 bytes --]
> > As per a request from the FSF, I have updated the copyright
> > headers of the non-FSF-copyrighted files from "GPL v2 or later"
> > to "GPL v3 or later".
>
> You can't do this without asking the copyright holders for
> permission first.
I was told the contrary by Karl Berry, and asked to change. IANAL,
but the "or (at your option) any later version" should give us the
right to do so, right?
That is correct, here is a snippet from the GPL FAQ. Though it is
only OK if the license either states "or any later version", or lacks
an explicit version -- then one may pick any version of the GPL.
| Why should programs say âVersion 2 of the GPL or any later versionâ?
|
| From time to time, at intervals of years, we change the
| GPLâsometimes to clarify it, sometimes to permit certain kinds of
| use not previously permitted, and sometimes to tighten up a
| requirement. (The last change was in 1991.) Using this âindirect
| pointerâ in each program makes it possible for us to change the
| distribution terms on the entire collection of GNU software, when
| we update the GPL.
|
| If each program lacked the indirect pointer, we would be forced to
| discuss the change at length with numerous copyright holders,
| which would be a virtual impossibility. In practice, the chance of
| having uniform distribution terms for GNU software would be nil.
|
| Suppose a program says âVersion 2 of the GPL or any later versionâ
| and a new version of the GPL is released. If the new GPL version
| gives additional permission, that permission will be available
| immediately to all the users of the program. But if the new GPL
| version has a tighter requirement, it will not restrict use of the
| current version of the program, because it can still be used under
| GPL version 2. When a program says âVersion 2 of the GPL or any
| later versionâ, users will always be permitted to use it, and even
| change it, according to the terms of GPL version 2âeven after
| later versions of the GPL are available.
|
| If a tighter requirement in a new version of the GPL need not be
| obeyed for existing software, how is it useful? Once GPL version 3
| is available, the developers of most GPL-covered programs will
| release subsequent versions of their programs specifying âVersion
| 3 of the GPL or any later versionâ. Then users will have to follow
| the tighter requirements in GPL version 3, for subsequent versions
| of the program.
|
| However, developers are not obligated to do this; developers can
| continue allowing use of the previous version of the GPL, if that
| is their preference.
next prev parent reply other threads:[~2012-12-20 18:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 7:26 Joel Brobecker
2012-12-19 8:50 ` Mark Kettenis
2012-12-19 9:05 ` Joel Brobecker
2012-12-19 11:18 ` Mark Kettenis
2012-12-19 11:25 ` Joel Brobecker
2012-12-19 11:38 ` Joel Brobecker
2012-12-20 18:20 ` Alfred M. Szmidt [this message]
2012-12-19 18:53 ` Mike Frysinger
2012-12-20 3:58 ` Joel Brobecker
2012-12-20 4:20 ` Joel Brobecker
2012-12-20 4:34 ` Mike Frysinger
2012-12-20 5:03 ` Joel Brobecker
2012-12-20 22:35 ` Mike Frysinger
2012-12-21 7:44 ` Joel Brobecker
2012-12-21 9:14 ` Eli Zaretskii
2012-12-21 11:38 ` Ralf Corsepius
2012-12-21 12:08 ` Joel Brobecker
2012-12-21 17:30 ` Mike Frysinger
2012-12-21 18:14 ` Joel Brobecker
2012-12-21 18:56 ` Mike Frysinger
2012-12-22 4:43 ` Joel Brobecker
2012-12-24 3:49 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Tlkj6-0008TE-12@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox