From: "Chris K. Jester-Young" <cky944@gmail.com>
To: guile-devel@gnu.org
Subject: Re: SRFI 41 for Guile
Date: Sat, 28 Jan 2012 02:00:24 -0500 [thread overview]
Message-ID: <20120128070024.GB7847@yarrow.destinee.acro.gen.nz> (raw)
In-Reply-To: <87r4zcibj2.fsf@pobox.com>
Hi Andy,
On Sat, Jan 07, 2012 at 01:47:29AM +0100, Andy Wingo wrote:
> Cky! Clearly I should have finished ploughing through guile-devel
> before we had the pleaseure of meeting up last week. Because if I had,
> I would have asked you to deliver two files: srfi-41.scm, and
> srfi-41.test :-)
Wow, I must have fallen off the edge of the world for the last 3+ weeks,
as I'm only just (vaguely) catching up with the list now. ;-) I haven't
forgotten about this. While I can't promise for it to be completed this
weekend, I will work on this as I find time to.
It was good meeting up! Hopefully we'll get another chance to do so. :-)
Cheers,
Chris.
prev parent reply other threads:[~2012-01-28 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 19:37 SRFI 41 for Guile Chris K. Jester-Young
2011-12-14 14:28 ` Ludovic Courtès
2011-12-16 6:45 ` Chris K. Jester-Young
2012-01-07 0:47 ` Andy Wingo
2012-01-28 7:00 ` Chris K. Jester-Young [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=20120128070024.GB7847@yarrow.destinee.acro.gen.nz \
--to=cky944@gmail.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).