From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21022 invoked by alias); 12 Jul 2007 11:33:34 -0000 Received: (qmail 20981 invoked by uid 22791); 12 Jul 2007 11:33:34 -0000 X-Spam-Check-By: sourceware.org Received: from cpc1-cmbg8-0-0-cust558.cmbg.cable.ntl.com (HELO zebedee.littlepinkcloud.COM) (82.6.106.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 12 Jul 2007 11:33:31 +0000 Received: from littlepinkcloud.COM (localhost.localdomain [127.0.0.1]) by zebedee.littlepinkcloud.COM (8.13.8/8.13.5) with ESMTP id l6CBXJMu025627; Thu, 12 Jul 2007 12:33:20 +0100 Received: (from aph@localhost) by littlepinkcloud.COM (8.13.8/8.13.5/Submit) id l6CBXI9a025624; Thu, 12 Jul 2007 12:33:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18070.4478.791089.519948@zebedee.pink> Date: Thu, 12 Jul 2007 11:33:00 -0000 From: Andrew Haley To: Nick Clifton Cc: Geoffrey Keating , gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org, binutils@sourceware.org Subject: Re: Changing top level files and include/ files over to GPLv3 In-Reply-To: <469610A7.6010806@redhat.com> References: <4695FF08.5060204@redhat.com> <251ADF2B-503D-4A80-BB45-D076559E6CC6@apple.com> <469610A7.6010806@redhat.com> X-Mailer: VM 7.19 under Emacs 22.0.93.1 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: 2007-07/txt/msg00189.txt.bz2 Nick Clifton writes: > Hi Geoff, > > > I think your copy is out-of-date, especially if it doesn't have a '2007' > > in the copyright years. > > Ah, yes, so it was. I am very sorry about that. > > >>> I presume this will include files licensed with an exception, > >> I had intended to files with license exceptions, but that has now changed. The GCC Steering Committee has decided to leave such files alone (for now), so I will not change them. > > It would be helpful to post the wording that is being considered. > > Umm, do you mean the wording that the GCC Steering committee is > considering to use as replacement text in files which currently use the > GPLv2 (or LGPLv2) but which also have an exception ? If so, then I am > sorry but I cannot help you. I do not know what wording they are > considering. I am sure that you can ask them though. AFAIAA the FSF hasn't yet sorted out the issue of GPLv3 + linking exception. We'll have to wait for them. Andrew.