unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: "Chris K. Jester-Young" <cky944@gmail.com>, guile-devel@gnu.org
Subject: Re: [PATCH] Add SRFI-41
Date: Thu, 21 Mar 2013 09:55:22 +0100	[thread overview]
Message-ID: <87ip4lxhc5.fsf@pobox.com> (raw)
In-Reply-To: <87li9hbn8m.fsf@tines.lan> (Mark H. Weaver's message of "Wed, 20 Mar 2013 20:38:49 -0400")

On Thu 21 Mar 2013 01:38, Mark H Weaver <mhw@netris.org> writes:

> Chris K. Jester-Young has been hard at work getting his SRFI-41
> implementation ready in time for Guile 2.0.8, and I think it might be
> ready to push.  What do you think?

Needs documentation.
-- 
http://wingolog.org/



  reply	other threads:[~2013-03-21  8:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21  0:38 [PATCH] Add SRFI-41 Mark H Weaver
2013-03-21  8:55 ` Andy Wingo [this message]
2013-03-27  2:53   ` Mark H Weaver
2013-03-27  3:00     ` Mark H Weaver
2013-03-27 17:43       ` Mark H Weaver
2013-03-27 20:58       ` 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=87ip4lxhc5.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=cky944@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.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).