From: Oleg <oleg_inconnu@myrealbox.com>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] Threats on future of Camlp4
Date: Sun, 6 Oct 2002 16:45:22 -0400 [thread overview]
Message-ID: <200210062045.QAA15753@apakabar.cc.columbia.edu> (raw)
In-Reply-To: <20021006220127.B20005@verdot.inria.fr>
On Sunday 06 October 2002 04:01 pm, Daniel de Rauglaudre wrote:
> Hi,
>
> On Sun, Oct 06, 2002 at 03:29:59PM -0400, Oleg wrote:
> > Could you explain what you mean by "compromising the future of Camlp4"?
> > I thought Camlp4 project was not affiliated with the O'Caml project /
> > team.
>
> It would be good, indeed, that Camlp4 be separated from OCaml, but
> the direction of the OCaml team refuses that energically. However
> it was a good compromise.
>
> He jeopardizes the future of Camlp4 because he gives me two choices:
> either return working on the ocaml/camlp4 version (what I refuse), or
> quit the projet. And if I quit the projet, who is going to improve
> Camlp4?
Daniel,
I'm still not sure I understand (BTW I did not know Camlp4 was being
integrated into O'Caml itself)
You are saying that "[integrating Camlp4 into O'Caml] was a good compromise",
but you are *also* saying that you are refusing to work on Camlp4 as part of
O'Caml. Why?
Pardon my ignorance, but is the offer to work on Camlp4 as part of O'Caml
some sort of demotion for you at INRIA, or is the whole conflict merely about
the location of Camlp4 in the CVS tree?
(I'm just curious as to what's going on)
Cheers
Oleg
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-10-06 20:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 18:55 Daniel de Rauglaudre
2002-10-06 19:23 ` Chris Hecker
2002-10-06 19:52 ` Daniel de Rauglaudre
2002-10-06 21:01 ` brogoff
2002-10-06 21:09 ` Daniel de Rauglaudre
2002-10-06 19:29 ` Oleg
2002-10-06 20:01 ` Daniel de Rauglaudre
2002-10-06 20:24 ` Alessandro Baretta
2002-10-06 20:24 ` Daniel de Rauglaudre
[not found] ` <200210062143.g96Lhix15834@orchestra.cs.caltech.edu>
2002-10-07 2:47 ` Daniel de Rauglaudre
2002-10-06 20:28 ` Dave Mason
2002-10-06 20:50 ` Daniel de Rauglaudre
2002-10-06 20:45 ` Oleg [this message]
2002-10-06 21:03 ` Daniel de Rauglaudre
2002-10-06 21:46 ` Florian Douetteau
2002-10-07 2:56 ` Daniel de Rauglaudre
2002-10-06 23:54 ` Markus Mottl
2002-10-07 9:06 ` Daniel de Rauglaudre
2002-10-11 11:34 ` Kontra, Gergely
2002-10-11 12:56 ` Alessandro Baretta
2002-10-11 13:15 ` [Caml-list] Future " Daniel de Rauglaudre
2002-10-12 21:45 ` Oleg
2002-10-13 9:02 ` Daniel de Rauglaudre
2002-10-11 16:36 ` [Caml-list] Syntax brogoff
2002-10-07 7:21 ` [Caml-list] Threats on future of Camlp4 Sven LUTHER
2002-10-07 8:52 ` Daniel de Rauglaudre
2002-10-07 11:25 ` Sven LUTHER
2002-10-07 11:30 ` Daniel de Rauglaudre
2002-10-07 11:55 ` Sven LUTHER
2002-10-08 7:57 ` Alessandro Baretta
[not found] ` <nhalm59cf0s.fsf@malabar.mitre.org>
2002-10-08 14:05 ` Alessandro Baretta
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=200210062045.QAA15753@apakabar.cc.columbia.edu \
--to=oleg_inconnu@myrealbox.com \
--cc=caml-list@inria.fr \
--cc=daniel.de_rauglaudre@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