Discussion:
What can I do to help?
Jacques Carette
2008-11-26 14:30:04 UTC
Permalink
Dear metaocaml-hackers,

Now that ocaml-3.11.0 is essentially on our doorstep, I would really
like to have metaocaml in sync with that. I am actively using metaocaml
in 2 projects now, and that is likely to increase in the future.

If another set of hands for re-merging basic metocaml with 3.11.0 would
help, I can do that.

Jacques
Walid Taha
2008-11-26 14:34:19 UTC
Permalink
Dear Jacques,

Thank you very much for this offer.

Cristiano: At this point, what do we need to do to bring MetaOCaml up to speed?

Walid.
Post by Jacques Carette
Dear metaocaml-hackers,
Now that ocaml-3.11.0 is essentially on our doorstep, I would really like to
have metaocaml in sync with that. I am actively using metaocaml in 2
projects now, and that is likely to increase in the future.
If another set of hands for re-merging basic metocaml with 3.11.0 would
help, I can do that.
Jacques
_______________________________________________
MetaOCaml-Hackers-L mailing list
https://mailman.rice.edu/mailman/listinfo/metaocaml-hackers-l
--
Walid Taha, Assistant Professor,
Department of Computer Science and Department of Electrical and
Computer Engineering
Rice University, MS-1302, Duncan Hall 3103, Houston, TX 77025
Tel: (832) 528 5948. Fax: (713) 583 9625

---

CONFIDENTIALITY NOTICE

The information in this email may be confidential and/or privileged. This
email is intended to be reviewed by only the individual or organization
named above. If you are not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
review, dissemination or copying of this email and its attachments, if any,
or the information contained herein is prohibited. If you have received this
email in error, please immediately notify the sender by return email and
delete this email from your system.
ccris
2008-11-26 15:23:25 UTC
Permalink
As usual, it's a matter of taking the diffs to the ocaml cvs
repository and apply them to the metaocaml repository, keeping an eye
on conflicts arising.
Hopefully, the changes do not affect metaocaml, but no silver bullet
there.

Cristiano
Post by Walid Taha
Dear Jacques,
Thank you very much for this offer.
Cristiano: At this point, what do we need to do to bring MetaOCaml up to speed?
Walid.
On Wed, Nov 26, 2008 at 8:30 AM, Jacques Carette
Post by Jacques Carette
Dear metaocaml-hackers,
Now that ocaml-3.11.0 is essentially on our doorstep, I would
really like to
have metaocaml in sync with that. I am actively using metaocaml in 2
projects now, and that is likely to increase in the future.
If another set of hands for re-merging basic metocaml with 3.11.0 would
help, I can do that.
Jacques
_______________________________________________
MetaOCaml-Hackers-L mailing list
https://mailman.rice.edu/mailman/listinfo/metaocaml-hackers-l
--
Walid Taha, Assistant Professor,
Department of Computer Science and Department of Electrical and
Computer Engineering
Rice University, MS-1302, Duncan Hall 3103, Houston, TX 77025
Tel: (832) 528 5948. Fax: (713) 583 9625
---
CONFIDENTIALITY NOTICE
The information in this email may be confidential and/or privileged. This
email is intended to be reviewed by only the individual or
organization
named above. If you are not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
review, dissemination or copying of this email and its attachments, if any,
or the information contained herein is prohibited. If you have
received this
email in error, please immediately notify the sender by return email and
delete this email from your system.
_______________________________________________
MetaOCaml-Hackers-L mailing list
https://mailman.rice.edu/mailman/listinfo/metaocaml-hackers-l
Jacques Carette
2008-11-26 15:29:01 UTC
Permalink
Is the metaocaml repository publicly available? Given the tag for the
ocaml cvs against which metaocaml was last synchronized, then if I got
access to the metaocaml repo, I could try this myself.

I must admit that I would want to use MetaOCaml_309_alpha_30 as my
'base' and keep concoqtion in a branch.

Jacques
Post by ccris
As usual, it's a matter of taking the diffs to the ocaml cvs
repository and apply them to the metaocaml repository, keeping an eye
on conflicts arising.
Hopefully, the changes do not affect metaocaml, but no silver bullet
there.
Cristiano
Jacques Carette
2008-11-26 15:34:59 UTC
Permalink
How about downloading the source from the web-page to keep things simple?
Sure, I can start from that.

Jacques
Jacques Carette
2008-11-27 04:09:03 UTC
Permalink
I have alpha_30, as well as full source trees for 3.09.1 and
3.11.0_rc1. I have gotten myself a list of patches to 'make' alpha_30
out of 3.09.1. I am now applying these, by hand, to 3.11.0_rc1.

I would estimate that I am about 1/3 done, although I think some of the
thorniest hand merges (like .depend) are behind me. I am also having to
be careful about dynamic loading, since that is now a feature of ocaml,
and I have to make sure that I do not include any of that from the
alpha_30 branch.
FYI, this is not the same as the current state of svn.
Is there any way you can get me a set of (context) diffs from alpha_30
to current svn? Even if there are glitches, that may still help me
figure out some oddities.

Note that right now I only intend to merge alpha_030 and ocaml 3.11.
Any other features from current svn [if I get the diffs or direct
access] will have to be done later; I will however consider backporting
bug fixes.

Jacques
Walid Taha
2008-11-27 05:47:23 UTC
Permalink
Jacques: I expect that all the differences are bug fixes.

Ron: Just to be sure, you are not looking at the concoqtion branch, right?
If we are sure about that, then it would probably be a good idea to make the
latest that's in the svn available to Jacques.

Also, please note that the internal version contains a script that needs to be
run before making a public release. I'll dig that info up as soon as I am back
(and I we are not in a hurry to make a public release at this point).

Emir: Can you confirm were the latest version should be, and where the
concoqtion branch lives?

Walid.
I have alpha_30, as well as full source trees for 3.09.1 and 3.11.0_rc1. I
have gotten myself a list of patches to 'make' alpha_30 out of 3.09.1. I am
now applying these, by hand, to 3.11.0_rc1.
I would estimate that I am about 1/3 done, although I think some of the
thorniest hand merges (like .depend) are behind me. I am also having to be
careful about dynamic loading, since that is now a feature of ocaml, and I
have to make sure that I do not include any of that from the alpha_30
branch.
FYI, this is not the same as the current state of svn.
Is there any way you can get me a set of (context) diffs from alpha_30 to
current svn? Even if there are glitches, that may still help me figure out
some oddities.
Note that right now I only intend to merge alpha_030 and ocaml 3.11. Any
other features from current svn [if I get the diffs or direct access] will
have to be done later; I will however consider backporting bug fixes.
Jacques
--
Walid Taha, Assistant Professor,
Department of Computer Science and Department of Electrical and
Computer Engineering
Rice University, MS-1302, Duncan Hall 3103, Houston, TX 77025
Tel: (832) 528 5948. Fax: (713) 583 9625

---

CONFIDENTIALITY NOTICE

The information in this email may be confidential and/or privileged. This
email is intended to be reviewed by only the individual or organization
named above. If you are not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
review, dissemination or copying of this email and its attachments, if any,
or the information contained herein is prohibited. If you have received this
email in error, please immediately notify the sender by return email and
delete this email from your system.
Ronald Garcia
2008-11-27 09:45:11 UTC
Permalink
Just to clarify, I'm looking at the ometa repository, as opposed to
the ometa-concoqtion repository.

By comparing the the release date of alpha_30 on the web page
(February 3, 2006) to the repository log , it looks like r5633
corresponds to alpha_30 (although the log for r5636 on Feb 6 mentions
polishing for distribution). After that, there are a few more
changes to the repository spread out over time.

If this information jives, I can make a tarball of the latest and
deliver it to Jacques.

ron
Post by Walid Taha
Jacques: I expect that all the differences are bug fixes.
Ron: Just to be sure, you are not looking at the concoqtion
branch, right?
If we are sure about that, then it would probably be a good idea to make the
latest that's in the svn available to Jacques.
Also, please note that the internal version contains a script that needs to be
run before making a public release. I'll dig that info up as soon as I am back
(and I we are not in a hurry to make a public release at this point).
Emir: Can you confirm were the latest version should be, and where the
concoqtion branch lives?
Walid.
On Wed, Nov 26, 2008 at 10:09 PM, Jacques Carette
Post by Jacques Carette
I have alpha_30, as well as full source trees for 3.09.1 and
3.11.0_rc1. I
have gotten myself a list of patches to 'make' alpha_30 out of 3.09.1. I am
now applying these, by hand, to 3.11.0_rc1.
I would estimate that I am about 1/3 done, although I think some of the
thorniest hand merges (like .depend) are behind me. I am also having to be
careful about dynamic loading, since that is now a feature of
ocaml, and I
have to make sure that I do not include any of that from the alpha_30
branch.
FYI, this is not the same as the current state of svn.
Is there any way you can get me a set of (context) diffs from
alpha_30 to
current svn? Even if there are glitches, that may still help me figure out
some oddities.
Note that right now I only intend to merge alpha_030 and ocaml 3.11. Any
other features from current svn [if I get the diffs or direct
access] will
have to be done later; I will however consider backporting bug fixes.
Jacques
--
Walid Taha, Assistant Professor,
Department of Computer Science and Department of Electrical and
Computer Engineering
Rice University, MS-1302, Duncan Hall 3103, Houston, TX 77025
Tel: (832) 528 5948. Fax: (713) 583 9625
---
CONFIDENTIALITY NOTICE
The information in this email may be confidential and/or
privileged. This
email is intended to be reviewed by only the individual or
organization
named above. If you are not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
review, dissemination or copying of this email and its attachments, if any,
or the information contained herein is prohibited. If you have
received this
email in error, please immediately notify the sender by return
email and
delete this email from your system.
Walid Taha
2008-11-27 10:02:41 UTC
Permalink
Good. You're looking at the right thing. This sounds like a plan.

Walid.
Just to clarify, I'm looking at the ometa repository, as opposed to the
ometa-concoqtion repository.
By comparing the the release date of alpha_30 on the web page (February 3,
2006) to the repository log , it looks like r5633 corresponds to alpha_30
(although the log for r5636 on Feb 6 mentions polishing for distribution).
After that, there are a few more changes to the repository spread out over
time.
If this information jives, I can make a tarball of the latest and deliver it
to Jacques.
ron
Post by Walid Taha
Jacques: I expect that all the differences are bug fixes.
Ron: Just to be sure, you are not looking at the concoqtion branch, right?
If we are sure about that, then it would probably be a good idea to make the
latest that's in the svn available to Jacques.
Also, please note that the internal version contains a script that needs to be
run before making a public release. I'll dig that info up as soon as I am back
(and I we are not in a hurry to make a public release at this point).
Emir: Can you confirm were the latest version should be, and where the
concoqtion branch lives?
Walid.
I have alpha_30, as well as full source trees for 3.09.1 and 3.11.0_rc1.
I
have gotten myself a list of patches to 'make' alpha_30 out of 3.09.1. I am
now applying these, by hand, to 3.11.0_rc1.
I would estimate that I am about 1/3 done, although I think some of the
thorniest hand merges (like .depend) are behind me. I am also having to be
careful about dynamic loading, since that is now a feature of ocaml, and I
have to make sure that I do not include any of that from the alpha_30
branch.
FYI, this is not the same as the current state of svn.
Is there any way you can get me a set of (context) diffs from alpha_30 to
current svn? Even if there are glitches, that may still help me figure out
some oddities.
Note that right now I only intend to merge alpha_030 and ocaml 3.11. Any
other features from current svn [if I get the diffs or direct access] will
have to be done later; I will however consider backporting bug fixes.
Jacques
--
Walid Taha, Assistant Professor,
Department of Computer Science and Department of Electrical and
Computer Engineering
Rice University, MS-1302, Duncan Hall 3103, Houston, TX 77025
Tel: (832) 528 5948. Fax: (713) 583 9625
---
CONFIDENTIALITY NOTICE
The information in this email may be confidential and/or privileged. This
email is intended to be reviewed by only the individual or organization
named above. If you are not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
review, dissemination or copying of this email and its attachments, if any,
or the information contained herein is prohibited. If you have received this
email in error, please immediately notify the sender by return email and
delete this email from your system.
--
Walid Taha, Assistant Professor,
Department of Computer Science and Department of Electrical and
Computer Engineering
Rice University, MS-1302, Duncan Hall 3103, Houston, TX 77025
Tel: (832) 528 5948. Fax: (713) 583 9625

---

CONFIDENTIALITY NOTICE

The information in this email may be confidential and/or privileged. This
email is intended to be reviewed by only the individual or organization
named above. If you are not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
review, dissemination or copying of this email and its attachments, if any,
or the information contained herein is prohibited. If you have received this
email in error, please immediately notify the sender by return email and
delete this email from your system.
Ronald Garcia
2008-11-27 10:05:42 UTC
Permalink
Great.

Jacques: I'll contact you off-list about getting you a snapshot of
the repository.

ron
Post by Walid Taha
Good. You're looking at the right thing. This sounds like a plan.
Walid.
On Thu, Nov 27, 2008 at 3:45 AM, Ronald Garcia
Just to clarify, I'm looking at the ometa repository, as opposed to the
ometa-concoqtion repository.
By comparing the the release date of alpha_30 on the web page
(February 3,
2006) to the repository log , it looks like r5633 corresponds to alpha_30
(although the log for r5636 on Feb 6 mentions polishing for
distribution).
After that, there are a few more changes to the repository spread out over
time.
If this information jives, I can make a tarball of the latest and deliver it
to Jacques.
ron
Post by Walid Taha
Jacques: I expect that all the differences are bug fixes.
Ron: Just to be sure, you are not looking at the concoqtion branch, right?
If we are sure about that, then it would probably be a good idea
to make
the
latest that's in the svn available to Jacques.
Also, please note that the internal version contains a script
that needs
to be
run before making a public release. I'll dig that info up as
soon as I am
back
(and I we are not in a hurry to make a public release at this point).
Emir: Can you confirm were the latest version should be, and where the
concoqtion branch lives?
Walid.
On Wed, Nov 26, 2008 at 10:09 PM, Jacques Carette
I have alpha_30, as well as full source trees for 3.09.1 and 3.11.0_rc1.
I
have gotten myself a list of patches to 'make' alpha_30 out of
3.09.1. I
am
now applying these, by hand, to 3.11.0_rc1.
I would estimate that I am about 1/3 done, although I think some of the
thorniest hand merges (like .depend) are behind me. I am also having to
be
careful about dynamic loading, since that is now a feature of
ocaml, and
I
have to make sure that I do not include any of that from the alpha_30
branch.
FYI, this is not the same as the current state of svn.
Is there any way you can get me a set of (context) diffs from alpha_30 to
current svn? Even if there are glitches, that may still help me
figure
out
some oddities.
Note that right now I only intend to merge alpha_030 and ocaml 3.11. Any
other features from current svn [if I get the diffs or direct
access]
will
have to be done later; I will however consider backporting bug fixes.
Jacques
--
Walid Taha, Assistant Professor,
Department of Computer Science and Department of Electrical and
Computer Engineering
Rice University, MS-1302, Duncan Hall 3103, Houston, TX 77025
Tel: (832) 528 5948. Fax: (713) 583 9625
---
CONFIDENTIALITY NOTICE
The information in this email may be confidential and/or
privileged. This
email is intended to be reviewed by only the individual or
organization
named above. If you are not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
review, dissemination or copying of this email and its
attachments, if
any,
or the information contained herein is prohibited. If you have
received
this
email in error, please immediately notify the sender by return email and
delete this email from your system.
--
Walid Taha, Assistant Professor,
Department of Computer Science and Department of Electrical and
Computer Engineering
Rice University, MS-1302, Duncan Hall 3103, Houston, TX 77025
Tel: (832) 528 5948. Fax: (713) 583 9625
---
CONFIDENTIALITY NOTICE
The information in this email may be confidential and/or
privileged. This
email is intended to be reviewed by only the individual or
organization
named above. If you are not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
review, dissemination or copying of this email and its attachments, if any,
or the information contained herein is prohibited. If you have
received this
email in error, please immediately notify the sender by return
email and
delete this email from your system.
Loading...