From: David Baelde <david.baelde@ens-lyon.org>
To: "Stéphane Glondu" <steph@glondu.net>
Cc: Romain Beauxis <toots@rastageeks.org>, caml-list@inria.fr
Subject: Re: [Caml-list] Uncaught Unix_error.
Date: Thu, 18 Jun 2009 22:16:04 +0200 [thread overview]
Message-ID: <53c655920906181316n3e3cd837s16327b4c6339f42a@mail.gmail.com> (raw)
In-Reply-To: <4A3A93B0.10907@glondu.net>
Thanks for all the details. The application does have support for
dynamically loading plugins but it's basically never used. We should
double check with the user (we can't reproduce) maybe he's loading
something funny...
--
David
next prev parent reply other threads:[~2009-06-18 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 12:16 Romain Beauxis
2009-06-18 13:17 ` [Caml-list] " Stéphane Glondu
2009-06-18 13:28 ` Romain Beauxis
2009-06-18 14:41 ` David Baelde
2009-06-18 16:47 ` Jake Donham
2009-06-18 19:21 ` Stéphane Glondu
2009-06-18 20:16 ` David Baelde [this message]
2009-06-19 13:23 ` Romain Beauxis
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=53c655920906181316n3e3cd837s16327b4c6339f42a@mail.gmail.com \
--to=david.baelde@ens-lyon.org \
--cc=caml-list@inria.fr \
--cc=steph@glondu.net \
--cc=toots@rastageeks.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 NNTP newsgroup(s).