From: Richard Jones <rich@annexia.org>
To: Jonathan Bryant <jtbryant@valdosta.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] type t = ()
Date: Fri, 10 Jun 2005 08:55:57 +0100 [thread overview]
Message-ID: <20050610075557.GA8145@furbychan.cocan.org> (raw)
In-Reply-To: <1118360624.17936.12.camel@chunky.valdosta.edu>
On Thu, Jun 09, 2005 at 07:43:44PM -0400, Jonathan Bryant wrote:
> Is this a question or a brief rant...? :)
Sort of a brief rant combined with a bug report :-)
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com
next prev parent reply other threads:[~2005-06-10 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 21:22 Richard Jones
2005-06-09 22:05 ` Vincenzo Ciancia
2005-06-10 12:56 ` [Caml-list] " Wolfgang Lux
2005-06-09 23:43 ` [Caml-list] " Jonathan Bryant
2005-06-10 7:55 ` Richard Jones [this message]
2005-06-10 13:02 ` Florian Hars
2005-06-10 22:12 ` Jon Harrop
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=20050610075557.GA8145@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=jtbryant@valdosta.edu \
/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).