From: Han-Wen Nienhuys <hanwenn@gmail.com>
To: ttn@gnuvola.org, Guile Devel <guile-devel@gnu.org>
Subject: Guile 1.8.9 release
Date: Tue, 12 Jan 2021 09:20:55 +0100 [thread overview]
Message-ID: <CAOw_e7Zh6Mr=7dDqT6kXHEHN=o_LjdFb7s5wV04J930d7XgVtQ@mail.gmail.com> (raw)
Hi Thien-Thi,
your timing is fortuitous. I just spent the christmas holidays delving
into GUILE 1.8's heap expansion strategy and found and fixed a bug
with it.
See
https://github.com/hanwen/guile/commit/9b32504780e0b604196be866b8c36079891e3cd6
How does code review for proposed patches work these days?
I'd be happy to polish it up (ie. add a proper test) for inclusion in
GUILE 1.8.9,
cheers,
--
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen
next reply other threads:[~2021-01-12 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 8:20 Han-Wen Nienhuys [this message]
2021-01-16 23:07 ` Guile 1.8.9 release Thien-Thi Nguyen
2021-01-17 18:37 ` Han-Wen Nienhuys
2021-02-09 8:59 ` Han-Wen Nienhuys
2021-02-10 22:17 ` Thien-Thi Nguyen
2021-02-14 10:35 ` Han-Wen Nienhuys
2021-03-14 9:34 ` Han-Wen Nienhuys
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='CAOw_e7Zh6Mr=7dDqT6kXHEHN=o_LjdFb7s5wV04J930d7XgVtQ@mail.gmail.com' \
--to=hanwenn@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ttn@gnuvola.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).