From: Taylan Kammer <taylan.kammer@gmail.com>
To: Matt Wette <matt.wette@gmail.com>, guile-user@gnu.org
Subject: bytestructures 2.0.1
Date: Tue, 22 Feb 2022 21:50:01 +0100 [thread overview]
Message-ID: <338a84ae-d7d8-d500-c608-7e5cadc50aa0@gmail.com> (raw)
In-Reply-To: <00f4e6be-3f2a-bd34-28ad-663346c333e5@gmail.com>
On 21.02.2022 22:09, Taylan Kammer wrote:
>
> It's already fixed upstream. Not sure if it's worth releasing 2.0.1.
>
Decided to release it after all. Just the test suite fix.
https://github.com/TaylanUB/scheme-bytestructures/releases/tag/v2.0.1
--
Taylan
next prev parent reply other threads:[~2022-02-22 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 19:51 bytestructures 2.0.0 Taylan Kammer
2022-02-20 23:25 ` Matt Wette
2022-02-21 21:09 ` Taylan Kammer
2022-02-22 20:50 ` Taylan Kammer [this message]
2022-02-23 21:36 ` bytestructures 2.0.1 Jérémy Korwin-Zmijowski
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=338a84ae-d7d8-d500-c608-7e5cadc50aa0@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=guile-user@gnu.org \
--cc=matt.wette@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).