From: Gerald Pfeifer <gerald@pfeifer.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Mark Mitchell <mark@codesourcery.com>, Mike Stump <mrs@apple.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Nick Clifton <nickc@redhat.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: Mon, 09 Jul 2007 15:11:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0707091703000.21810@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <orhcodn24w.fsf@oliva.athome.lsd.ic.unicamp.br>
On Mon, 9 Jul 2007, Alexandre Oliva wrote:
> At which point I wonder why someone would have problems upgrading the
> license of an earlier GCC code base. Can anyone list any reasons why
> this upgrade would be objectionable, considering that it was widely
> (?) known that GCC (and any other FSF-owned code) would upgrade to
> GPLv3 pretty much as soon as it was available?
I am not sure the customers of $X will appreciate a license change of
this kind with a point release, let a alone a customer-specific bug fix
release (or delaying the latter for legal review). And the same holds
for OEMs.
Feel free to replace $X by "your employer", "my employer", or the name
of any other significant GCC distributor. :-)
Gerald
next prev parent reply other threads:[~2007-07-09 15:11 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 [this message]
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
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=Pine.LNX.4.64.0707091703000.21810@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=mark@codesourcery.com \
--cc=mrs@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