Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/GPLv3] Add COPYING3 to gdb
Date: Wed, 08 Aug 2007 19:24:00 -0000	[thread overview]
Message-ID: <ulkclg8v8.fsf@gnu.org> (raw)
In-Reply-To: <20070808181156.GA20477@adacore.com> (message from Joel Brobecker 	on Wed, 8 Aug 2007 11:11:56 -0700)

> Date: Wed, 8 Aug 2007 11:11:56 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> 
> I think the first step into moving to GPL v3 is to add a file named
> COPYING3 that contains a copy of the GPL v3 licensing terms.

Why COPYING3? why not just COPYING?

> I looked at the GCC sources, and this is what they did.

Emacs calls this file COPYING, not COPYING3.

> The GPL v2 license was still kept in COPYING.

Why do we need to keep GPL v2?

> The next steps are bulk updates of the headers in the source files.
> I propose the following header, which is a modified version of the
> current ones, and slightly modeled on the GCC ones as well (for the
> later part that talks about how to obtain the license terms).
> 
>    This program is free software; you can redistribute it and/or modify
>    it under the terms of the GNU General Public License as published by
>    the Free Software Foundation; either version 2 of the License, or
>    (at your option) any later version.
> 
>    This program is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>    GNU General Public License for more details.
> 
>    You should have received a copy of the GNU General Public License
>    along with GCC; see the file COPYING3.  If not see
>    <http://www.gnu.org/licenses/>.
> 
> Would that be an acceptable header?

Sorry, I don't understand why we need to change the current wording,
and why does the above mention GPL v2 instead of v3.  Could you please
explain?


  parent reply	other threads:[~2007-08-08 19:24 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 [this message]
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
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=ulkclg8v8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.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