From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Merging R6RS libraries?
Date: Sat, 22 May 2010 15:51:45 +0200 [thread overview]
Message-ID: <87zkzst572.fsf@gnu.org> (raw)
In-Reply-To: AANLkTikHiYfpYJykvtYTEYTpjfkJuc8wfGyvo3cB02Xs@mail.gmail.com
Hello!
Julian Graham <joolean@gmail.com> writes:
> Thanks to Andy's heroic work on the expander over the past week or so,
> I've just been able to merge `wip-r6rs-libraries' into `master' and
> push it!
Cool, congratulations to both of you!
> As you'll notice from running `make check', there are still a few
> issues to be addressed -- specifically, the implementation of `div'
> and `mod' [0]. Anyone have any thoughts?
Not quite, but I trust you’ll find out. ;-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-05-22 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 21:27 Merging R6RS libraries? Ludovic Courtès
2010-03-29 23:06 ` Julian Graham
2010-04-11 3:50 ` Julian Graham
2010-04-11 21:49 ` Andy Wingo
2010-05-21 2:04 ` Julian Graham
2010-05-22 13:51 ` Ludovic Courtès [this message]
2010-03-30 17:59 ` Mike Gran
2010-03-30 21:53 ` 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=87zkzst572.fsf@gnu.org \
--to=ludo@gnu.org \
--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).