From: Joel Reymont <joelr1@gmail.com>
To: Gabriel Kerneis <gabriel.kerneis@enst.fr>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Help with new camlp4
Date: Mon, 2 Apr 2007 14:54:22 +0100 [thread overview]
Message-ID: <1A450036-B136-44E3-A15F-6D27D26F16CD@gmail.com> (raw)
In-Reply-To: <E1HYMsP-0000nP-3z@tatanka.kerneis.info>
On Apr 2, 2007, at 2:47 PM, Gabriel Kerneis wrote:
> It changed a few days ago. Look at the end of
> ocaml/camlp4/examples/lambda_quot.ml
There must be something wrong with my cvs. I'm doing cvs update in
the tree and it's not pulling in new camlp4 examples.
--
http://wagerlabs.com/
next prev parent reply other threads:[~2007-04-02 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 8:33 Joel Reymont
2007-04-02 9:14 ` [Caml-list] " Nicolas Pouillard
2007-04-02 9:21 ` Joel Reymont
2007-04-02 9:23 ` Joel Reymont
2007-04-02 9:28 ` Nicolas Pouillard
2007-04-02 12:24 ` Joel Reymont
2007-04-02 12:30 ` Joel Reymont
2007-04-02 13:47 ` Gabriel Kerneis
2007-04-02 13:54 ` Joel Reymont [this message]
2007-04-02 17:15 ` Nicolas Pouillard
2007-04-02 12:40 ` Joel Reymont
2007-04-02 12:44 ` Joel Reymont
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=1A450036-B136-44E3-A15F-6D27D26F16CD@gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=gabriel.kerneis@enst.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).