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

On Wed, 04 Jun 2003 09:43:32 -0400, Kelley Cook <kcook34@ford.com> said:

>>> Date: Tue, 3 Jun 2003 15:32:58 -0400
>>> From: Nathanael Nerode <neroden@twcny.rr.com>

>>> I'm opposed to the GFDL, particularly with "Invariant Sections"

>> Can you tell why?

> Please do not continue this subthread on the gdb, gcc, or binutils
> lists as is it is not on-topic.

> A lively discussion on this topic which does include RMS, has been
> going on the Debian-Legal ListServ
> (http://lists.debian.org/debian-legal/) for months now.

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...

David Carlton
carlton@math.stanford.edu

  reply	other threads:[~2003-06-04 17:25 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 [this message]
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=ro1of1dg3g8.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=gdb@sources.redhat.com \
    --cc=kcook34@ford.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).