From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: SRFI 61: a more general `cond' clause
Date: Tue, 06 Dec 2005 22:53:02 +0200 [thread overview]
Message-ID: <87psoa3q35.fsf@zagadka.de> (raw)
In-Reply-To: <1122953031.16783.34.camel@nocandy.dyndns.org> (Stephen Compall's message of "Mon, 01 Aug 2005 22:23:51 -0500")
Stephen Compall <s11@member.fsf.org> writes:
> Attached is a version with the suggested doc move and no more
> srfi-61.scm. Thanks for your recommendations.
Applied, thanks!
Do you have any test cases for this?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2005-12-06 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 0:25 SRFI 61: a more general `cond' clause Stephen Compall
2005-07-30 1:22 ` Stephen Compall
[not found] ` <878xzlrywd.fsf@zip.com.au>
[not found] ` <1122953031.16783.34.camel@nocandy.dyndns.org>
2005-12-06 20:53 ` Marius Vollmer [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=87psoa3q35.fsf@zagadka.de \
--to=mvo@zagadka.de \
--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).