public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: gdb@sources.redhat.com
Subject: Re: Libiberty licensing problems & solutions [DRAFT]
Date: Wed, 04 Jun 2003 18:01:00 -0000	[thread overview]
Message-ID: <ro165nlg1s4.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <ro1of1dg3g8.fsf@jackfruit.Stanford.EDU>

On 04 Jun 2003 10:25:27 -0700, David Carlton <carlton@math.stanford.edu> said:

> Thanks for the reference; interesting.  I'm not at all impressed by
> the FSF's behavior in this instance. :-(  Of course, it's not like
> I've been contributing much to GDB's manual in the first place...

And, for that matter, I have no idea if the one contribution to the
manual that I made is valid.  I don't have a copy of the assignment
that I initially signed at hand, but more recent assigments that I
have around say things like:

+   The Released Category comprises

+ (a) changes and enhancements to software already (as of the time such
+ change or enhancement is made) freely circulating under stated terms
+ permitting public redistribution, whether in the public domain, or
+ under the FSF's GNU General Public License, or under the FSF's GNU
+ Lesser General Public License (a.k.a. the GNU Library General Public
+ License), or under other such terms; and

Documentation isn't software, and even if it were, the GFDL isn't
mentioned explicitly, and I personally wouldn't consider the GFDL to
be "other such terms" (e.g. it's not GPL-compatible).  So if that's
supposed to cover changes to manuals licensed under the GFDL, then it
seems to me that, at the very least, the FSF should make that more
explicit.

Sigh.

David Carlton
carlton@math.stanford.edu

  reply	other threads:[~2003-06-04 18:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 19:33 Nathanael Nerode
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 [this message]
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=ro165nlg1s4.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=gdb@sources.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).