From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Why bother porting Guile to BDW-GC?
Date: Tue, 11 Nov 2008 21:32:18 +0100 [thread overview]
Message-ID: <m3od0matrh.fsf@pobox.com> (raw)
In-Reply-To: <87skpyrpka.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 11 Nov 2008 21:11:01 +0100")
On Tue 11 Nov 2008 21:11, ludo@gnu.org (Ludovic Courtès) writes:
> I think the best we can do is keep the thing in a separate branch.
Sure.
> Does that seem like a reasonable plan?
Some benchmarking would be really nice ;-)
Like these for example:
http://www.ccs.neu.edu/home/will/Twobit/benchmarksAbout.html
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2008-11-11 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 15:58 Why bother porting Guile to BDW-GC? Ludovic Courtès
2008-11-09 2:23 ` Han-Wen Nienhuys
2008-11-09 2:27 ` Han-Wen Nienhuys
2008-11-09 18:25 ` Ludovic Courtès
2008-11-10 20:57 ` Neil Jerram
2008-11-11 20:11 ` Ludovic Courtès
2008-11-11 20:32 ` Andy Wingo [this message]
2008-11-12 8:28 ` Ludovic Courtès
2008-11-10 21:10 ` Ludovic Courtès
2008-11-11 20:42 ` Ludovic Courtès
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=m3od0matrh.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).