Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: DJ Delorie <dj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/GPLv3] Add COPYING3 to gdb
Date: Fri, 10 Aug 2007 14:51:00 -0000	[thread overview]
Message-ID: <u3ayrfnol.fsf@gnu.org> (raw)
In-Reply-To: <xnmyx0mhff.fsf@greed.delorie.com> (message from DJ Delorie on 09 	Aug 2007 19:12:04 -0400)

> Cc: gdb-patches@sourceware.org
> From: DJ Delorie <dj@redhat.com>
> Date: 09 Aug 2007 19:12:04 -0400
> 
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> > Doesn't version 3 fit the "version 2 or later" clause?
> 
> IANAL, but IMHO...
> 
> The old license allows us to *distribute* under newer terms.
> 
> It does not allow us to actually change the license.
> 
> I think this means that if we distribute a GPL2+ program to someone
> under the terms of GPL3, the program itself is still under the terms
> of GPL2+.

Perhaps there's a misunderstanding.  I didn't suggest to change the
blurb in the files.  All I suggested is replace the file COPYING we
have now (which is GPL v2 text) with GPL v3 text, without changing the
name of the file, so it's still COPYING.

This way, the files that are under "version 2 or later" are still
okay, since we distribute them under GPL v3.

Okay?


  parent reply	other threads:[~2007-08-10 14:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 18:08 Joel Brobecker
2007-08-08 18:17 ` Daniel Jacobowitz
2007-08-08 19:24 ` Eli Zaretskii
2007-08-08 19:28   ` Daniel Jacobowitz
2007-08-09  3:07     ` Eli Zaretskii
2007-08-09  3:27       ` Joel Brobecker
2007-08-09 22:13         ` Eli Zaretskii
2007-08-09 11:29       ` Daniel Jacobowitz
2007-08-09 22:14         ` Eli Zaretskii
2007-08-09 23:12           ` DJ Delorie
2007-08-10  2:39             ` Daniel Jacobowitz
2007-08-10 14:51             ` Eli Zaretskii [this message]
2007-08-10 15:47               ` Joel Brobecker
2007-08-10 16:45                 ` Eli Zaretskii
2007-08-10 18:01                   ` Daniel Jacobowitz

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=u3ayrfnol.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dj@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