From: Doug Evans <dje@transmeta.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
Andrew Cagney <cagney@redhat.com>,
binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: [rfa] FRV input files
Date: Wed, 07 May 2003 19:19:00 -0000 [thread overview]
Message-ID: <16057.23584.595530.27519@casey.transmeta.com> (raw)
In-Reply-To: <3EB95197.70405@redhat.com>
Andrew Cagney writes:
> Having the FSF distribute this code under anything other than the
> standard GPL would be an "improvised license change".
Ah, so if I wanted to add, say, a regexp package to Binutils releases
and use it in libopcodes, I'd have to make it GPL right?
[no answers from the peanut gallery please, I want to hear Andrew's opinion]
> I [wearing a Red Hat] can't dictate the licencing terms under which the
> FSF distributes these FSF (C) files.
Strawman. Who said anything about dictating.
> > Also, I'm not sure I want *.cpu to say it's part of Binutils.
>
> A file identified as being part of "binutils", is covered by an FSF
> "binutils" assignment. This makes everyones life a lot easier.
Easier for who and why?
next prev parent reply other threads:[~2003-05-07 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3EB31259.8050603@redhat.com>
2003-05-03 1:07 ` Doug Evans
2003-05-03 1:10 ` Doug Evans
[not found] ` <3EB40A72.1060304@redhat.com>
2003-05-03 20:37 ` Doug Evans
[not found] ` <3EB43D55.7000508@redhat.com>
2003-05-03 23:21 ` Doug Evans
2003-05-04 11:27 ` Frank Ch. Eigler
2003-05-04 15:13 ` Andrew Cagney
2003-05-05 13:36 ` Frank Ch. Eigler
2003-05-06 21:42 ` Andrew Cagney
2003-05-07 16:20 ` Doug Evans
2003-05-07 18:34 ` Andrew Cagney
2003-05-07 19:19 ` Doug Evans [this message]
2003-05-07 19:46 ` Andrew Cagney
2003-05-07 19:56 ` Andrew Cagney
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=16057.23584.595530.27519@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=cagney@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).