public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: DJ Delorie <dj@redhat.com>
Cc: mrs@apple.com, neroden@twcny.rr.com, gcc@gcc.gnu.org,
	gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: Libiberty license roundup (questions/potential problems)
Date: Wed, 28 May 2003 21:10:00 -0000	[thread overview]
Message-ID: <3ED50D8E.4070405@redhat.com> (raw)
In-Reply-To: <200305240134.h4O1YTc21104@greed.delorie.com>

>> > * No license, FSF copyright
>> >   vfprintf.c
>> > 
>> > This was written by us for us.  I think it should be GPL with exception.
> 
>> 
>> GPL.
> 
> 
> We've already had a few cases where we've had to convert GPL to GPL
> with exception.  It might be prudent of us to, if we're fiddling with
> copyrights anyway, to start with GPL+e this time.  Especially with the
> trivial functions, where there is little to be gained by enforcing the
> GPL and a lot to be gained by making it easy for people to justify
> using GNU software.

It is always easier to weaken a license.  I think it is easierr to start 
with something safe.

Andrew


  reply	other threads:[~2003-05-28 19:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 23:06 Nathanael Nerode
2003-05-23 23:16 ` DJ Delorie
2003-05-24  1:23 ` Mike Stump
2003-05-24  1:32   ` Andrew Cagney
2003-05-24  1:37     ` DJ Delorie
2003-05-28 21:10       ` Andrew Cagney [this message]
2003-05-28 22:25         ` Joe Buck
2003-05-30 17:37 ` David O'Brien
2003-05-30 19:05   ` DJ Delorie
2003-05-24  4:07 Nathanael Nerode
2003-05-24 14:07 ` DJ Delorie
2003-05-24  7:08 Nathanael Nerode
2003-05-24 14:59 Robert Dewar
2003-05-28 22:50 Robert Dewar
2003-05-28 23:58 ` Joe Buck
2003-05-29  0:10 Robert Dewar

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=3ED50D8E.4070405@redhat.com \
    --to=ac131313@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=mrs@apple.com \
    --cc=neroden@twcny.rr.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).