Convert README to Markdown #47
Comments
|
To put it bluntly: I cannot care less. However, I'm ready to accept lightweight formatting (that does not prevent reading it comfortably as text in emacs). |
ejgallego
added a commit
to ejgallego/lablgtk
that referenced
this issue
Feb 12, 2019
After 3.0.beta4, the loose constraints should mostly work; depending on the changes we do of course. We also update the `homepage` field of the OPAM files, and the CHANGES file, if I understand correctly this should indeed make `dune-release` work out of the box [and to produce sensible changelogs] This fixes garrigue#47. Note that dune-release was incorrectly reading `CHANGES.API` to create the OPAM changelog! So I had to fix that too.
ejgallego
added a commit
to ejgallego/lablgtk
that referenced
this issue
Feb 12, 2019
After 3.0.beta4, the loose constraints should mostly work; depending on the changes we do of course. We also update the `homepage` field of the OPAM files, and the CHANGES file, if I understand correctly this should indeed make `dune-release` work out of the box [and to produce sensible changelogs] This fixes garrigue#47. Note that dune-release was incorrectly reading `CHANGES.API` to create the OPAM changelog! So I had to fix that too.
ejgallego
added a commit
to ejgallego/lablgtk
that referenced
this issue
Feb 12, 2019
After 3.0.beta4, the loose constraints should mostly work; depending on the changes we do of course. We also update the `homepage` field of the OPAM files, and the CHANGES file, if I understand correctly this should indeed make `dune-release` work out of the box [and to produce sensible changelogs] This fixes garrigue#47. Note that dune-release was incorrectly reading `CHANGES.API` to create the OPAM changelog! So I had to fix that too.
ejgallego
added a commit
to ejgallego/lablgtk
that referenced
this issue
Feb 12, 2019
After 3.0.beta4, the loose constraints should mostly work; depending on the changes we do of course. We also update the `homepage` field of the OPAM files, and the CHANGES file, if I understand correctly this should indeed make `dune-release` work out of the box [and to produce sensible changelogs] This fixes garrigue#47. Note that dune-release was incorrectly reading `CHANGES.API` to create the OPAM changelog! So I had to fix that too.
ejgallego
added a commit
to ejgallego/lablgtk
that referenced
this issue
Feb 12, 2019
After 3.0.beta4, the loose constraints should mostly work; depending on the changes we do of course. We also update the `homepage` field of the OPAM files, and the CHANGES file, if I understand correctly this should indeed make `dune-release` work out of the box [and to produce sensible changelogs] This fixes garrigue#47. Note that dune-release was incorrectly reading `CHANGES.API` to create the OPAM changelog! So I had to fix that too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe it makes sense also to modernize the README look for the first lablgtk3 release?
The text was updated successfully, but these errors were encountered: