Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add manual #78

Merged
merged 75 commits into from
May 4, 2016
Merged

Add manual #78

merged 75 commits into from
May 4, 2016

Conversation

gasche
Copy link
Member

@gasche gasche commented May 2, 2016

This merges
https://github.com/gasche/manual-ocamlbuild/
under a new manual subdirectory.

@bobot
Copy link
Collaborator

bobot commented May 4, 2016

Great! I read rapidly the manual-ocamlbuild thread, and it should definitely go to this repository. Just could you add a commit that moves the CONTRIBUTING.md file to the top dir?

Thanks to all the participants!

gasche and others added 27 commits May 4, 2016 07:33
I’m not certain this is a grammar error, but it feels like one because
the two clauses of the “and” do not have the same structure.
Technically there was no grammar error, but there didn’t seem to be any
benefit to avoiding multiple sentences. Originally I was going to
replace the en dash with an em dash, but then realized it could just be
a new sentence.
My fix is what I suspect you intended, use of em dashes to insert a
parenthetical statement.
I’m not enough of a linguist to know which language rule is being
broken here, but I suspect “those” is incorrect here.
I read “_tags” as “underscore tags”, in which case “an” is required.
I try to avoid starting sentences with lowercase words. This isn’t
always possible, but I think it is here.
* Replace Markdown with Asciidoctor markup.
* Make a distinct CONTRIBUTING.adoc document, following GitHub conventions.
* Use a tabular presentation in manual where more appropriate than past
  presentation.
* Add a directory for incomplete code samples, samples/.
* First work towards sourcing incomplete code samples instead of including them
  verbatim in the manual text.
* Be more consistent in use of `ocamlbuild` vs. OCamlbuild. For any tool now,
 `tool` is used when the CLI utility is meant vs. Tool when software product
  as a whole is meant.
* Add TODO comments in manual for existing parts that need expert attention.
(with Changes from Gabriel Scherer)
@gasche
Copy link
Member Author

gasche commented May 4, 2016

Thanks for the feedback, I updated and moved the CONTRIBUTING document, I'll merge.

@gasche gasche merged commit ccf52ea into ocaml:master May 4, 2016
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.

8 participants