From: Kevin Ryde <user42@zip.com.au>
Subject: r5rs_pitfall.test license
Date: Sat, 17 Jan 2004 23:52:10 +1000 [thread overview]
Message-ID: <87u12u65th.fsf@zip.com.au> (raw)
I noticed r5rs_pitfall.test is missing a license statement, I guess it
just wants a copy of the usual lgpl notice.
There seems to be a lot of different people credited for the various
parts. I hope the copyright notice saying just the FSF is right.
It's probably worth saying "Ideas by XYZ" as suggested by the gnu
maintainer guide, to separate who the coding is by and who the ideas
are by.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-01-17 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 13:52 Kevin Ryde [this message]
2004-02-17 21:18 ` r5rs_pitfall.test license 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=87u12u65th.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).