Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Haley <aph-gcc@littlepinkcloud.COM>
To: Nick Clifton <nickc@redhat.com>
Cc: Geoffrey Keating <geoffk@apple.com>,
	gcc-patches@gcc.gnu.org,         gdb-patches@sourceware.org,
	binutils@sourceware.org
Subject: Re: Changing top level files and include/ files over to GPLv3
Date: Thu, 12 Jul 2007 11:33:00 -0000	[thread overview]
Message-ID: <18070.4478.791089.519948@zebedee.pink> (raw)
In-Reply-To: <469610A7.6010806@redhat.com>

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.


      reply	other threads:[~2007-07-12 11:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 18:06 Nick Clifton
2007-07-06 18:25 ` Mark Kettenis
2007-07-06 18:34   ` Daniel Jacobowitz
2007-07-06 19:36     ` Joel Brobecker
2007-07-06 20:55       ` Daniel Jacobowitz
2007-07-09  9:47         ` Nick Clifton
2007-07-09 17:25           ` Joel Brobecker
2007-07-06 20:21 ` Joseph S. Myers
2007-07-06 20:31   ` DJ Delorie
2007-07-09 13:59     ` Alexandre Oliva
2007-07-06 20:51   ` Mike Stump
2007-07-06 21:11     ` Mark Mitchell
2007-07-09 13:23       ` Alexandre Oliva
2007-07-09 15:11         ` Gerald Pfeifer
2007-07-09 16:41           ` Alexandre Oliva
2007-07-09 17:06             ` Corinna Vinschen
2007-07-09 17:56               ` Alexandre Oliva
2007-07-09 19:45                 ` Corinna Vinschen
2007-07-06 21:12   ` Russ Allbery
2007-07-11  1:56 ` Geoffrey Keating
2007-07-12 10:14   ` Nick Clifton
2007-07-12 10:16     ` Nick Clifton
2007-07-12 11:00     ` Geoffrey Keating
2007-07-12 11:30       ` Nick Clifton
2007-07-12 11:33         ` Andrew Haley [this message]

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=18070.4478.791089.519948@zebedee.pink \
    --to=aph-gcc@littlepinkcloud.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=geoffk@apple.com \
    --cc=nickc@redhat.com \
    /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