From: Nathanael Nerode <neroden@twcny.rr.com>
To: jsm28@cam.ac.uk
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: Libiberty licensing problems & solutions [DRAFT]
Date: Tue, 03 Jun 2003 19:33:00 -0000 [thread overview]
Message-ID: <20030603193258.GA32189@doctormoo> (raw)
Joseph Myers said:
>Apart from this, libiberty manual licensing is a mess in other ways
I'm not touching the manual licensing at the moment. I'm opposed to the
GFDL, particularly with "Invariant Sections", and so I'm not going to do
anything to help it.
I may request that the manual be relicensed at some point, but I'm
trying to separate that from the hopefully non-controversial
relicensings I'm discussing in my draft letter.
--Nathanael
next reply other threads:[~2003-06-03 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 19:33 Nathanael Nerode [this message]
2003-06-04 3:27 ` Eli Zaretskii
2003-06-04 13:55 ` <20030603193258.GA32189@doctormoo> <7458-Wed04Jun2003062758+0300-eliz@elta.co.il> Kelley Cook
2003-06-04 13:52 ` Libiberty licensing problems & solutions [DRAFT] Kelley Cook
2003-06-04 17:25 ` David Carlton
2003-06-04 18:01 ` David Carlton
2003-06-04 17:35 ` Mike Stump
-- strict thread matches above, loose matches on Subject: below --
2003-06-03 17:36 Nathanael Nerode
2003-06-03 18:34 ` Joseph S. Myers
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=20030603193258.GA32189@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jsm28@cam.ac.uk \
/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).