From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org, Greg Troxel <gdt@ir.bbn.com>
Subject: Re: 1.8 status
Date: Mon, 14 Aug 2006 09:44:50 +1000 [thread overview]
Message-ID: <87r6zkryj1.fsf@zip.com.au> (raw)
In-Reply-To: <87hd0h36g8.fsf@raven.defaultvalue.org> (Rob Browning's message of "Sat, 12 Aug 2006 16:00:39 -0700")
Rob Browning <rlb@defaultvalue.org> writes:
>
> So far, the only patch I know is going in is one to fix the
> numbers.test failure.
The array-set! breakage on bitvectors is bad too,
* unif.c (bitvector_set): Use h->writable_elements not h->elements.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-08-13 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 16:38 1.8 status Greg Troxel
2006-08-10 16:48 ` Bruce Korb
2006-08-10 23:06 ` Kevin Ryde
2006-08-12 23:00 ` Rob Browning
2006-08-13 23:44 ` Kevin Ryde [this message]
2006-08-14 17:22 ` Greg Troxel
-- strict thread matches above, loose matches on Subject: below --
2006-03-26 13:02 Neil Jerram
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=87r6zkryj1.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=gdt@ir.bbn.com \
--cc=guile-devel@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).