From: "Nicolas Cannasse" <warplayer@free.fr>
To: "skaller" <skaller@users.sourceforge.net>,
"Matt Gushee" <mgushee@havenrock.com>
Cc: <caml-list@inria.fr>
Subject: Re: Build errors (was Re: [Caml-list] Neko 1.0)
Date: Thu, 18 Aug 2005 20:43:28 +0200 [thread overview]
Message-ID: <00cd01c5a424$b951a240$0100a8c0@warp> (raw)
In-Reply-To: <1124389592.8402.53.camel@localhost.localdomain>
Please report theses through the Neko mailling list.
Although I wish they were, I'm not sure the whole CamlList people are
interested in Neko build errors on 64-bit platforms ;)
Nicolas
next prev parent reply other threads:[~2005-08-18 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 9:06 Neko 1.0 Nicolas Cannasse
2005-08-18 14:33 ` [Caml-list] " Matt Gushee
2005-08-18 14:51 ` Matt Gushee
[not found] ` <014e01c5a406$45a30dc0$ef01a8c0@warp>
2005-08-18 15:12 ` Matt Gushee
2005-08-18 15:41 ` Build errors (was Re: [Caml-list] Neko 1.0) Matt Gushee
2005-08-18 18:22 ` skaller
2005-08-18 18:26 ` skaller
2005-08-18 18:43 ` Nicolas Cannasse [this message]
2005-08-18 18:41 ` Nicolas Cannasse
2005-08-18 20:39 ` Sven Luther
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='00cd01c5a424$b951a240$0100a8c0@warp' \
--to=warplayer@free.fr \
--cc=caml-list@inria.fr \
--cc=mgushee@havenrock.com \
--cc=skaller@users.sourceforge.net \
/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).