From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFC] what should we do about COPYING?
Date: Fri, 18 Dec 2009 17:43:00 -0000 [thread overview]
Message-ID: <200912181743.02168.pedro@codesourcery.com> (raw)
In-Reply-To: <4B2BBD07.2020408@vmware.com>
On Friday 18 December 2009 17:33:59, Michael Snyder wrote:
> Joel Brobecker wrote:
> > Michael Snyder pointed out that gdb/COPYING contains the GPLv2,
> > whereas GDB is now under GPLv3. I was simply going to replace the
> > contents of COPYING with the GPLv3, except that I noticed an
> > inconsistent resolution depending on the project. For instance:
> >
> > - In the root directory, we have COPYING (v2) and COPYING3 (v3);
> > - In bfd, we have COPYING that contains the GPL v3.
> >
> > I personally do not see the point of keeping the GPL v2 around,
> > and thus suggest that we replace the contents COPYING rather than
> > adding an extra file named COPYING3. Note that we have a couple
> > of extra copies in the sim directory as well.
> >
>
> I agree. v2 COPYING should just go.
Note that there is code in sim that is v2 or later, copyrighted Andrew Cagney, not FSF.
Also, in gdb/ it appears some new gplv2 or later files have crept
in:
>grep "version 2 of" * -rn
ChangeLog-2003:15347: again by default on systems with version 2 of the GNU C library.
configure:1605: systems with version 2 of the GNU C library (use
configure.ac:928: AS_HELP_STRING([--without-included-regex], [don't use included regex; this is the default on systems with version 2 of the GNU C library (use with caution on other system)]),
COPYING:299: the Free Software Foundation; either version 2 of the License, or
darwin-nat-info.c:11: the Free Software Foundation; either version 2 of the License, or
doc/Makefile.in:9:# the Free Software Foundation; either version 2 of the License, or
doc/gpl.texi:359:the Free Software Foundation; either version 2 of the License, or
doc/observer.texi:14:@c Foundation; either version 2 of the License, or (at your option)
features/Makefile:7:# the Free Software Foundation; either version 2 of the License, or
regformats/regdat.sh:103: the Free Software Foundation; either version 2 of the License, or
solib-spu.c:10: the Free Software Foundation; either version 2 of the License, or
spu-multiarch.c:10: the Free Software Foundation; either version 2 of the License, or
testsuite/gdb.ada/gnat_ada.gpr:5:-- the Free Software Foundation; either version 2 of the License, or
testsuite/gdb.java/jprint.java:13:// the Free Software Foundation; either version 2 of the License, or
testsuite/gdb.base/source-error.gdb:7:# the Free Software Foundation; either version 2 of the License, or
testsuite/gdb.base/gcore-buffer-overflow.c:7: the Free Software Foundation; either version 2 of the License, or (at
testsuite/gdb.base/gcore-buffer-overflow.exp:5:# the Free Software Foundation; either version 2 of the License, or
testsuite/gdb.base/watch_thread_num.c:7: the Free Software Foundation; either version 2 of the License, or
testsuite/gdb.mi/mi-async.exp:5:# the Free Software Foundation; either version 2 of the License, or
testsuite/gdb.modula2/unbounded-array.exp:5:# the Free Software Foundation; either version 2 of the License, or
testsuite/gdb.modula2/unbounded1.c:7: the Free Software Foundation; either version 2 of the License, or
What's the story behind gpl.texi?
--
Pedro Alves
next prev parent reply other threads:[~2009-12-18 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 7:33 Joel Brobecker
2009-12-18 15:52 ` Stan Shebs
2009-12-18 17:36 ` Michael Snyder
2009-12-18 17:43 ` Pedro Alves [this message]
2009-12-20 12:20 ` Joel Brobecker
2009-12-20 12:33 ` Alfred M. Szmidt
2009-12-20 14:27 ` Stan Shebs
2009-12-21 7:55 ` Joel Brobecker
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=200912181743.02168.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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