From: Mark H Weaver <mhw@netris.org>
To: nalaginrut <nalaginrut@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Release time!
Date: Tue, 06 Nov 2012 01:05:02 -0500 [thread overview]
Message-ID: <87bofbclm9.fsf@tines.lan> (raw)
In-Reply-To: <1352167575.2654.18.camel@Renee-desktop.suse> (nalaginrut@gmail.com's message of "Tue, 06 Nov 2012 10:06:15 +0800")
nalaginrut <nalaginrut@gmail.com> writes:
> And don't forget SRFI-105 ;-D
SRFI-105 is already in.
Mark
next prev parent reply other threads:[~2012-11-06 6:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 18:11 Release time! Ludovic Courtès
2012-11-05 20:13 ` Hans Aberg
2012-11-05 21:02 ` Ludovic Courtès
2012-11-05 21:48 ` Hans Aberg
2012-11-06 18:28 ` Ludovic Courtès
2012-11-06 21:23 ` Hans Aberg
2012-11-05 20:53 ` Ludovic Courtès
2012-11-05 22:38 ` Bruce Korb
2012-11-06 18:29 ` Ludovic Courtès
2012-11-06 2:06 ` nalaginrut
2012-11-06 6:05 ` Mark H Weaver [this message]
2012-11-06 18:30 ` Ludovic Courtès
2012-11-06 5:59 ` Mark H Weaver
2012-11-06 18:41 ` Ludovic Courtès
2012-11-06 21:35 ` Ian Price
2012-11-07 0:01 ` Andreas Rottmann
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=87bofbclm9.fsf@tines.lan \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=nalaginrut@gmail.com \
/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).