Update the list of possible values for ocaml_version in the README #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
+ a link to the wiki documenting the correspondence with coq_version.
|
Merging now as a follow-up of #43 |
|
LGTM but shouldn't there be some warning that not all OCaml versions are available with all Coq versions? |
Indeed, I will push a small remark in |
erikmd
added a commit
that referenced
this pull request
Dec 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Kind: this is a documentation-only PR.
@Zimmi48 could you have a look at this PR and merge it if you approve it? (or directly modify the branch if need be!)
indeed given coq-community/docker-coq#23, it appears it'd be good to document the current state of supported
ocaml_versions from Docker-Coq in the master README (in the same way as I had documented the on-going change in the docker-coq wiki) and this, even if #39 which will bring yet more documentation, is not yet ready.