From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [RFA/GPLv3] Add COPYING3 to gdb
Date: Thu, 09 Aug 2007 03:07:00 -0000 [thread overview]
Message-ID: <uk5s5fltq.fsf@gnu.org> (raw)
In-Reply-To: <20070808192803.GA17053@caradoc.them.org> (message from Daniel Jacobowitz on Wed, 8 Aug 2007 15:28:03 -0400)
> Date: Wed, 8 Aug 2007 15:28:03 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
>
> > Why COPYING3? why not just COPYING?
>
> One reason is that there are some files which refer to COPYING whose
> license text we can not change. For instance, parts of sim are
> copyright Andrew Cagney rather than the FSF - and I believe other
> simulators are copyright various corporations. They're all "version 2
> or later", so it is not a problem, but we do not have authority to
> change the license statements in them.
Sorry, I still don't get it: if those files refer to COPYING and are
"version 2 or later", then it sounds like having GPL v3 in a file
named "COPYING" is actually TRT to do, isn't it?
What am I missing?
next prev parent reply other threads:[~2007-08-09 3:07 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 [this message]
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=uk5s5fltq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--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