From: Andreas Rottmann <a.rottmann@gmx.at>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Add implementation of SRFI 27
Date: Fri, 01 Oct 2010 00:37:52 +0200 [thread overview]
Message-ID: <871v8a503j.fsf@delenn.lan> (raw)
In-Reply-To: <877hi5q0qg.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 28 Sep 2010 18:41:43 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Andreas Rottmann <a.rottmann@gmx.at> writes:
>
>> +@c This subsection is based on the specification of SRFI-27, which has
>> +@c the following license:
>> +
>> +@c Copyright (C) Sebastian Egner (2002). All Rights Reserved.
>
> Perhaps this should appear in the text, perhaps with a link to the
> license or something?
>
Indeed, I will put something along these lines into the text, including
a link to the original specification (which includes the license text at
its end). Expect a patch sometime soon.
A slightly related question: I'm preparing patches to add SRFI 42 and
67. I don't know if I'll find the time and motivation to also provide a
texinfo version of their specifications (and, contrary to SRFI 27, these
would essentially be literal transcriptions). Would patches which just
add links to the documents at http://srfi.schemers.org/ into the manual
at the appropriate places be acceptable as well?
Regards, Rotty
--
Andreas Rottmann -- <http://rotty.yi.org/>
next prev parent reply other threads:[~2010-09-30 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 21:10 [PATCH] Add implementation of SRFI 27 Andreas Rottmann
2010-09-27 20:23 ` Andy Wingo
2010-09-28 16:41 ` Ludovic Courtès
2010-09-30 22:37 ` Andreas Rottmann [this message]
[not found] ` <1255814696.192356.1285886306079.JavaMail.root@zmbs1.inria.fr>
2010-10-01 9:02 ` Ludovic Courtès
2010-10-01 13:59 ` Andy Wingo
2010-10-03 22:04 ` Andreas Rottmann
[not found] ` <389630629.239319.1285941376781.JavaMail.root@zmbs1.inria.fr>
2010-10-01 16:14 ` Ludovic Courtès
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=871v8a503j.fsf@delenn.lan \
--to=a.rottmann@gmx.at \
--cc=guile-devel@gnu.org \
--cc=ludo@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).