From: Andy Wingo <wingo@pobox.com>
To: "Juhani Viheräkoski" <moonshine@kapsi.fi>
Cc: guile-devel@gnu.org
Subject: Re: simplex.scm fails after recent changes in master
Date: Wed, 16 Sep 2009 21:04:12 +0200 [thread overview]
Message-ID: <m38wged843.fsf@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0908151449460.16144@lakka.kapsi> ("Juhani Viheräkoski"'s message of "Sat, 15 Aug 2009 14:54:17 +0300 (EEST)")
Hi Juhani,
On Sat 15 Aug 2009 13:54, Juhani Viheräkoski <moonshine@kapsi.fi> writes:
> [simplex] now seems to run forever when compiled but works with the
> interpreter. It used to work when I last tried, that was maybe a week
> ago.
This was fixed in 7f7b85cbf68a8b83e1ad7bc78379cf2764fc9a1b. Thanks for
the report!
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2009-09-16 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 11:54 simplex.scm fails after recent changes in master Juhani Viheräkoski
2009-09-16 19:04 ` Andy Wingo [this message]
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=m38wged843.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=moonshine@kapsi.fi \
/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).