From: Carl Witty <cwitty@newtonlabs.com>
Cc: guile-devel@gnu.org
Subject: Re: doc license section
Date: 21 Jan 2004 14:04:42 -0800 [thread overview]
Message-ID: <1074722682.3851.47.camel@flare> (raw)
In-Reply-To: <87y8s19d9i.fsf@zagadka.ping.de>
On Wed, 2004-01-21 at 13:56, Marius Vollmer wrote:
> Kevin Ryde <user42@zip.com.au> writes:
>
> > Might be worth thinking about GFDL for the manuals, while on the
> > subject of licenses.
>
> Yes, indeed. Maintain.texi says: "Manuals should use the GNU Free
> Documentation License".
Be aware that the feeling on the debian-legal mailing list is that the
GFDL is not sufficiently free for materials in Debian (for a number of
reasons which I personally find compelling). See
http://people.debian.org/%7Esrivasta/Position_Statement.xhtml for more
information (or read the debian-legal archives). It is likely that
GFDL-licensed materials will be removed from Debian after the next
Debian release.
(Marius: my e-mail message that mentioned "double-checked locking"
bounced from your ping.de address:
(reason: 553 direct mail from dialups not accepted here)
I think there's something wrong with the filtering there, because the
e-mail was sent from my corporate e-mail server, which is definitely not
a dialup.)
Carl Witty
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-21 22:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 0:30 doc license section Kevin Ryde
2004-01-15 2:12 ` Stephen Compall
2004-01-20 0:46 ` Kevin Ryde
2004-01-15 21:37 ` Neil Jerram
2004-01-21 21:56 ` Marius Vollmer
2004-01-21 22:04 ` Carl Witty [this message]
2004-01-21 22:58 ` Kevin Ryde
2004-01-21 23:07 ` Marius Vollmer
2004-01-21 23:22 ` Marius Vollmer
2004-01-22 18:08 ` Pierre Bernatchez
2004-01-22 18:22 ` Paul Jarc
2004-01-22 23:18 ` Marius Vollmer
2004-01-21 22:13 ` Kevin Ryde
2004-01-21 22:40 ` Neil Jerram
2004-02-18 20:34 ` Marius Vollmer
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1074722682.3851.47.camel@flare \
--to=cwitty@newtonlabs.com \
--cc=guile-devel@gnu.org \
/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).