Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFC] what should we do about COPYING?
Date: Fri, 18 Dec 2009 07:33:00 -0000	[thread overview]
Message-ID: <20091218073249.GC2788@adacore.com> (raw)

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.

-- 
Joel


             reply	other threads:[~2009-12-18  7:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  7:33 Joel Brobecker [this message]
2009-12-18 15:52 ` Stan Shebs
2009-12-18 17:36 ` Michael Snyder
2009-12-18 17:43   ` Pedro Alves
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=20091218073249.GC2788@adacore.com \
    --to=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