caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocaml 3.07 patch
Date: Fri, 3 Oct 2003 11:48:00 +0200	[thread overview]
Message-ID: <20031003094800.GA24515@iliana> (raw)
In-Reply-To: <20031003111219.A29512@pauillac.inria.fr>

On Fri, Oct 03, 2003 at 11:12:19AM +0200, Xavier Leroy wrote:
> In response to the Camlp4 issues (with labeled arguments) that were
> discovered in release 3.07 of OCaml: Michel Mauny has been working
> hard on correcting the issues, and I just made available a patch
> against the 3.07 sources:
> 
>       http://caml.inria.fr/distrib/ocaml-3.07/ocaml-3.07-patch1.diffs
> 
> It would be great if the users who where affected by the problem could
> give it a try and let us (caml@inria.fr) know how it goes.
> (Users who track the CVS repository can use it instead.)

So i suppose this is the same as the one in CVS. I have had reports from
Maxence that this solves the cameleon build problem, but you may already
know that, and indeed it fixed also the problem showing up in planets.

> If the issues are fixed, I'll update the binary distributions to
> incorporate the patch.  Making binary distributions takes a

So you will just do a new version of 3.07 ? What about bumbing the
version number to 3.07.1 or something such ?

> surprisingly long time, and is boring, so I'd rather not do that too
> often...

Would this be the right oportunity to open a bugfix branch in the CVS ?
This would make it easier for ocaml distributors to track the important
fixes out of the CVS, and make sure the fixed versions of ocaml floating
around are in a somewhat consistent state, and that some important fix
may or may not be applied to some of them.

I understand that you are afraid that this will cause you more work,
because you have to test both version, but i think that this may not be
that problematic as you fear, since the number of fixes to this branch
will usually be not that numerous, and you can also rely on the
distributors to do some of the testing for you.

This would make live easier for all ocaml user, and is a feature that is
needed for ocaml to be more professionally perceived.

Friendly,

Sven Luther

-------------------
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


      reply	other threads:[~2003-10-03  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03  9:12 Xavier Leroy
2003-10-03  9:48 ` Sven Luther [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=20031003094800.GA24515@iliana \
    --to=sven.luther@wanadoo.fr \
    --cc=caml-list@inria.fr \
    --cc=xavier.leroy@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).