From: Mike Gran <spk121@yahoo.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-user@gnu.org
Subject: Re: [ANN] guile-gi 0.0.2 released
Date: Mon, 17 Jun 2019 06:09:43 -0700 [thread overview]
Message-ID: <20190617130943.GA15241@spikycactus.attlocal.net> (raw)
In-Reply-To: <877e9kpgox.fsf@elephly.net>
On Mon, Jun 17, 2019 at 01:57:50PM +0200, Ricardo Wurmus wrote:
>
> Hi Mike,
>
> > Hello. I am announcing guile-gi v0.0.2.
>
> Yay! Thank you.
>
> I updated the package in Guix and noticed that the test for
> atomic_int_set is marked as XFAIL, but it now passes. In Guix we now
> override the list of XFAIL_TESTS to let the tests pass.
Thank you. It is quite interesting that it should pass in another
environment.
-Mike
next prev parent reply other threads:[~2019-06-17 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 19:20 [ANN] guile-gi 0.0.2 released Mike Gran
2019-06-16 19:40 ` Mike Gran
2019-06-16 20:06 ` sirgazil
2019-06-16 20:49 ` Mark H Weaver
2019-06-17 11:57 ` Ricardo Wurmus
2019-06-17 13:09 ` Mike Gran [this message]
[not found] <mailman.81.1560787249.14391.guile-user@gnu.org>
2019-06-17 22:39 ` Zelphir Kaltstahl
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=20190617130943.GA15241@spikycactus.attlocal.net \
--to=spk121@yahoo.com \
--cc=guile-user@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).