From: Maxime Devos <maximedevos@telenet.be>
To: Andy Wingo <wingo@pobox.com>,
guile-user@gnu.org, guile-sources@gnu.org, guile-devel@gnu.org
Subject: Re: GNU Guile 3.0.8 released
Date: Fri, 11 Feb 2022 12:05:23 +0100 [thread overview]
Message-ID: <fac9829f1d6a34a22a61986c100b7354a6202fde.camel@telenet.be> (raw)
In-Reply-To: <87zgmxn8t7.fsf@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Andy Wingo schreef op vr 11-02-2022 om 08:47 [+0100]:
> We are delighted to announce GNU Guile release 3.0.8, the latest in the [...]
> The Guile 3.0.8 release mixes maintenance and optimizations [...]
Is there any reason the fix
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43521#11> was not
applied?
In the future, could it be announced in advance that a new version will
be released? Then people could test the new proposed version and remind
maintainers of forgotten fixes before the version has been finalised.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-11 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 7:47 GNU Guile 3.0.8 released Andy Wingo
2022-02-11 11:05 ` Maxime Devos [this message]
2022-02-11 17:14 ` Aleix Conchillo Flaqué
2022-02-11 18:03 ` Ricardo Wurmus
2022-02-12 1:28 ` Greg Troxel
2022-02-12 2:04 ` Aleix Conchillo Flaqué
2022-02-11 14:34 ` [PP?] " Olivier Dion via Developers list for Guile, the GNU extensibility library
-- strict thread matches above, loose matches on Subject: below --
2022-02-12 13:54 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=fac9829f1d6a34a22a61986c100b7354a6202fde.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=guile-sources@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).