From: Marius Vollmer <mvo@zagadka.de>
Cc: bug-guile@gnu.org
Subject: Re: Problem with random numbers on the EM64T platform
Date: Tue, 21 Feb 2006 01:08:11 +0200 [thread overview]
Message-ID: <87d5hhy6g4.fsf@zagadka.de> (raw)
In-Reply-To: <66e540fe0602190836t56a9557du9422bfe1b923ffef@mail.gmail.com> (Mikael Djurfeldt's message of "Sun, 19 Feb 2006 17:36:08 +0100")
"Mikael Djurfeldt" <mdjurfeldt@gmail.com> writes:
> I've now fixed this in CVS HEAD:
Thanks! I 'ported' your fix to the relase_1-8 branch and it is in
1.8.0.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2006-02-20 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 15:49 Problem with random numbers on the EM64T platform Mikael Djurfeldt
2006-02-19 16:36 ` Mikael Djurfeldt
2006-02-20 23:08 ` Marius Vollmer [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=87d5hhy6g4.fsf@zagadka.de \
--to=mvo@zagadka.de \
--cc=bug-guile@gnu.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).