From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: doco srfi-1 iota
Date: Sat, 12 Jul 2003 08:43:19 +1000 [thread overview]
Message-ID: <87k7aoit14.fsf@zip.com.au> (raw)
In-Reply-To: <16137.65380.115639.994664@localhost.localdomain> (Han-Wen Nienhuys's message of "Tue, 8 Jul 2003 01:16:52 +0200")
Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
>
> which begs the question, why aren't the SRFIs themselves used as
> documentation?
Oh, well, I suppose redoing it matches the format of the rest of the
manual, and allows nice indexing and cross references.
In any case I made this particular change.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-07-11 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 21:57 doco srfi-1 iota Kevin Ryde
2003-07-07 23:16 ` Han-Wen Nienhuys
2003-07-11 22:43 ` Kevin Ryde [this message]
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=87k7aoit14.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).