From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20051 invoked by alias); 20 Dec 2012 18:20:24 -0000 Received: (qmail 20035 invoked by uid 22791); 20 Dec 2012 18:20:22 -0000 X-SWARE-Spam-Status: No, hits=-7.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (208.118.235.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 20 Dec 2012 18:20:13 +0000 Received: from ams by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1Tlkj6-0008TE-12; Thu, 20 Dec 2012 13:20:12 -0500 Date: Thu, 20 Dec 2012 18:20:00 -0000 Message-Id: From: ams@gnu.org (Alfred M. Szmidt) To: Joel Brobecker CC: mark.kettenis@xs4all.nl, gdb-patches@sourceware.org In-reply-to: <20121219090457.GT3273@adacore.com> (message from Joel Brobecker on Wed, 19 Dec 2012 13:04:58 +0400) Subject: Re: Update some sim copyright headers to GPLv3-or-later Reply-to: ams@gnu.org References: <20121219072641.GQ3273@adacore.com> <201212190850.qBJ8oiUb030909@glazunov.sibelius.xs4all.nl> <20121219090457.GT3273@adacore.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-12/txt/msg00756.txt.bz2 > > 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.