From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: GNU Guile 3.0.10 released
Date: Sun, 30 Jun 2024 22:42:06 -0400 [thread overview]
Message-ID: <87r0cd96kh.fsf@gmail.com> (raw)
In-Reply-To: <877cef2uhk.fsf@pobox.com> (Andy Wingo's message of "Sun, 23 Jun 2024 23:56:55 +0200")
Hi Andy and other Guile maintainers,
Andy Wingo <wingo@pobox.com> writes:
> We are pleased to announce GNU Guile release 3.0.10, the latest in the
> 3.0 stable release series.
>
> Guile 3.0.10 is a bug-fix release which also adds optimizations, support
> for a new WebAssembly back-end, new custom port facilities, a new
> optional front-end syntax, and more. See the NEWS extract at the end of
> the mail for full details.
[...]
Wow, thank you for writing this detailed release news
entry, and for making the release happen! It seems to be packed with
many interesting improvements, I look forward to using it.
--
Thanks,
Maxim
prev parent reply other threads:[~2024-07-01 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 21:56 GNU Guile 3.0.10 released Andy Wingo
2024-06-24 9:54 ` Linus Björnstam
2024-07-01 2:42 ` Maxim Cournoyer [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=87r0cd96kh.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.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).