From: Alexandre Oliva <aoliva@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: Changing top level files and include/ files over to GPLv3
Date: Mon, 09 Jul 2007 17:56:00 -0000 [thread overview]
Message-ID: <orzm25ii0s.fsf@oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20070709170650.GP6851@calimero.vinschen.de> (Corinna Vinschen's message of "Mon\, 9 Jul 2007 19\:06\:50 +0200")
On Jul 9, 2007, Corinna Vinschen <vinschen@redhat.com> wrote:
> This isn't quite correct. v3 adds restrictions which were not present
> in v2.
Can you name any that doesn't arguably qualify as a "further
restriction" already prohibited by section 6 of GPLv2?
That it plugs potential ambiguities is what makes it incompatible.
These are not really new requirements.
> That's why linking v3 and v2-only stuff violates v2-only, but not
> v3.
Linking v3 and v2-only violates both. They're mutually-incompatible.
GPLv2 adds requirements on top of GPLv3, and GPLv3 removes ambiguities
present in GPLv2, which some frame as new requirements.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2007-07-09 17:56 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 [this message]
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=orzm25ii0s.fsf@oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gdb-patches@sourceware.org \
/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