Skip to content

Conversation

@kit-ty-kate
Copy link
Contributor

As said in #5

@gasche
Copy link
Contributor

gasche commented Jun 13, 2014

I suppose the best thing to do would be to do a release without this patch, for people that don't use the latest PG'OCaml and may want to get the nice fixes in the current trunk, and then do a second release with the change, so that the new release (and trunk) would require 2.0 from now on. Do you agree?

@kit-ty-kate
Copy link
Contributor Author

Ok, why not. I just fixed some bugs in the _oasis.
I'm checking if all is working first.

@kit-ty-kate
Copy link
Contributor Author

@ocsigen-buildbot test this please

@kit-ty-kate
Copy link
Contributor Author

All seems ok for me (modulo my comment on #17).

@kit-ty-kate kit-ty-kate mentioned this pull request Sep 30, 2014
kit-ty-kate added a commit that referenced this pull request Oct 1, 2014
Update against the latest pgocaml
@kit-ty-kate kit-ty-kate merged commit 8b942f3 into master Oct 1, 2014
@kit-ty-kate kit-ty-kate deleted the pgocaml-sync branch October 1, 2014 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants