From: Neil Jerram <neil@ossau.homelinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: GNU Guile 2.0.4 released
Date: Mon, 30 Jan 2012 21:27:49 +0000 [thread overview]
Message-ID: <87wr88q3sa.fsf@neil-laptop.ossau.uklinux.net> (raw)
In-Reply-To: <87ty3c51x1.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 30 Jan 2012 22:13:46 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> ... and I forgot to bump the SONAME. :-/
>
> I guess I have to push a 2.0.5 tarball now? Thoughts?
I'm afraid I've forgotten the implications of that...
But congratulations and thanks for the release anyway; for my FFI
hacking I particularly appreciate the fixes related to
procedure->pointer and GC.
Neil
next prev parent reply other threads:[~2012-01-30 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 20:56 GNU Guile 2.0.4 released Ludovic Courtès
2012-01-30 21:13 ` Ludovic Courtès
2012-01-30 21:27 ` Neil Jerram [this message]
2012-01-30 21:43 ` Hans Aberg
2012-01-30 22:15 ` Ludovic Courtès
2012-01-31 9:41 ` Andy Wingo
2012-01-31 13:20 ` Ludovic Courtès
2012-01-31 13:46 ` Andy Wingo
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=87wr88q3sa.fsf@neil-laptop.ossau.uklinux.net \
--to=neil@ossau.homelinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@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).