From: Fabrice Le Fessant <fabrice.le_fessant@inria.fr>
To: Jeremy Fincher <fincher.8@osu.edu>
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] What's the proper way to release ocaml projects?
Date: Tue, 23 Oct 2001 12:47:41 +0200 (CEST) [thread overview]
Message-ID: <15317.19149.258511.407314@lachesis.inria.fr> (raw)
In-Reply-To: <20011022175711.A51427@functor.resnet.ohio-state.edu>
One way is to integrate it in the CDK (Caml Development
Kit). Currently, it is a manual process :) You send me an URL to your
source files (libraries), that I will modify to compile inside the
CDK. Programs can be given also under the 'examples" part in your
libraries.
Regards,
- Fabrice
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-10-23 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 21:57 Jeremy Fincher
2001-10-23 10:47 ` Fabrice Le Fessant [this message]
2001-10-23 17:24 ` Maxence Guesdon
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=15317.19149.258511.407314@lachesis.inria.fr \
--to=fabrice.le_fessant@inria.fr \
--cc=caml-list@pauillac.inria.fr \
--cc=fincher.8@osu.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).