From: Sven <luther@dpt-info.u-strasbg.fr>
To: Cuihtlauac ALVARADO <cuihtlauac.alvarado@francetelecom.com>
Cc: Ian Zimmerman <itz@speakeasy.org>, OCAML <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: No /usr/bin/ocamltags in current ocaml package
Date: Thu, 17 Jan 2002 11:36:47 +0100 [thread overview]
Message-ID: <20020117113647.B14830@dpt-info.u-strasbg.fr> (raw)
In-Reply-To: <20020117112848.D1034@francetelecom.com>; from cuihtlauac.alvarado@francetelecom.com on Thu, Jan 17, 2002 at 11:28:48AM +0100
On Thu, Jan 17, 2002 at 11:28:48AM +0100, Cuihtlauac ALVARADO wrote:
> I'm not so sure to get it all right, but it reminds me that we forgot
> to announce the new Otags release (for Ocaml 3.04). Jean-Francois has
> just finished to upload it at :
>
> http://moninjf.multimania.com/Ocaml/otags-3.04.tar.gz
>
> Nothing very new in this release, except the version number which
> matches Ocaml's. We've tested it on Coq V7.2, it worked.
>
> Like the last version it is now stand alone, you don't need anything
> but Ocaml to compile.
>
> Hope it can help; comments, bugs and misc. are wellcome.
Note that it is already part of a debian package, it comes with ocaml-tools
which include also other nice stuff that are not part of the official ocaml
release.
Friendly,
Sven Luther
-------------------
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
prev parent reply other threads:[~2002-01-17 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yhxg056pwuz.fsf@lully.bgx.airsys.thomson-csf.com>
[not found] ` <20020116162506.A7475@dpt-info.u-strasbg.fr>
[not found] ` <yhxlmeynwdh.fsf@lully.bgx.airsys.thomson-csf.com>
2002-01-16 16:21 ` Ian Zimmerman
2002-01-16 17:09 ` Cuihtlauac ALVARADO
2002-01-16 17:40 ` Sven
2002-01-17 10:28 ` Cuihtlauac ALVARADO
2002-01-17 10:36 ` Sven [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=20020117113647.B14830@dpt-info.u-strasbg.fr \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=cuihtlauac.alvarado@francetelecom.com \
--cc=itz@speakeasy.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).