From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-email@systemreboot.net
Subject: Re: [guile-email] Ready for Guile 3.0?
Date: Mon, 16 Dec 2019 02:23:25 +0530 [thread overview]
Message-ID: <cu7mubtl396.fsf@systemreboot.net> (raw)
Message-ID: <20191215205325.Qgym0EgJs-9KHrcd3xRy9YCys97z2KCGj6akwncZE-A@z> (raw)
In-Reply-To: <877e2xdglz.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 451 bytes --]
> Unfortunately, guile-email does not seem to pass its tests when built
> with Guile 3.
Oops, I totally forgot about this! Thanks for the reminder!
The issues were mostly minor issues to do with the test driver,
autotools use, etc. I have fixed them all now. Please check with the
latest commit on the master branch.
I guess you're only using a git checkout of guile-email. But anyway, I
will publish a new minor release of guile-email in a week.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-12-15 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 10:32 Ricardo Wurmus
2019-12-15 20:53 ` Arun Isaac [this message]
2019-12-15 20:53 ` Arun Isaac
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7mubtl396.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guile-email@systemreboot.net \
--cc=rekado@elephly.net \
/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