From: Richard Jones <rich@annexia.org>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] We should all be forking
Date: Thu, 7 Jun 2007 13:04:19 +0100 [thread overview]
Message-ID: <20070607120419.GA20497@furbychan.cocan.org> (raw)
In-Reply-To: <200706051913.13481.jon@ffconsultancy.com>
How close are we to real-time raytracing then? Given that 4 & even 8
core machines may become commonplace soon.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2007-06-07 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 18:13 Jon Harrop
2007-06-05 18:25 ` [Caml-list] " Jonathan Bryant
2007-06-05 18:32 ` Joel Reymont
2007-06-05 18:46 ` Jon Harrop
2007-06-05 19:13 ` Chris King
2007-06-05 19:20 ` jocaml vs camlp3l Joel Reymont
2007-06-05 21:02 ` [Caml-list] " Erik de Castro Lopo
2007-06-05 23:58 ` [Caml-list] We should all be forking Brian Hurt
2007-06-07 12:04 ` Richard Jones [this message]
2007-06-14 10:09 ` Luc Maranget
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070607120419.GA20497@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=jon@ffconsultancy.com \
/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 NNTP newsgroup(s).