From: "Berke Durak" <berke.durak@gmail.com>
To: "David Teller" <David.Teller@univ-orleans.fr>
Cc: "Caml List" <caml-list@inria.fr>
Subject: Re: extlib on OCamlCore.org (was: [Caml-list] forge.OCamlCore.org is now ready to serve the OCaml community)
Date: Mon, 21 Apr 2008 16:30:46 +0200 [thread overview]
Message-ID: <b903a8570804210730t3eae99c0u33f9e0ca734d18ac@mail.gmail.com> (raw)
In-Reply-To: <1208693757.6316.16.camel@Blefuscu>
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
David Teller:
> That's planned. The exact list of syntax extensions will need to be
> discussed. I believe noone will contest including open_in .
Open_in should be fine.
Could you add Sexplib to the list?
--
Berke
[-- Attachment #2: Type: text/html, Size: 328 bytes --]
prev parent reply other threads:[~2008-04-21 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 0:08 Hezekiah M. Carty
2008-04-20 2:42 ` Peng Zang
2008-04-20 12:15 ` David Teller
2008-04-21 14:30 ` Berke Durak [this message]
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=b903a8570804210730t3eae99c0u33f9e0ca734d18ac@mail.gmail.com \
--to=berke.durak@gmail.com \
--cc=David.Teller@univ-orleans.fr \
--cc=caml-list@inria.fr \
/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).