From: Jacques-Pascal Deplaix <jp.deplaix@gmail.com>
To: Jeremy Yallop <yallop@gmail.com>,
Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: caml users <caml-list@inria.fr>,
"platform@lists.ocaml.org" <platform@lists.ocaml.org>
Subject: Re: [Caml-list] [ocaml-platform] [ANN] Experiment: OCaml patch review on github.com/ocaml/ocaml
Date: Tue, 08 Apr 2014 14:59:13 +0200 [thread overview]
Message-ID: <5343F2A1.8020209@gmail.com> (raw)
In-Reply-To: <CAAxsn=GFAbSeJqu0qW4YYM08Diq=sEgC+7ziuBLOR5RDQxMWOw@mail.gmail.com>
I'm a little skeptical for the name of this repository. I think «
ocamldoc » should be reserved to the tool.
Maybe « documentation » or « manual » would be better.
Cheers,
On 04/08/2014 02:37 PM, Jeremy Yallop wrote:
> On 30 January 2014 11:34, Gabriel Scherer <gabriel.scherer@gmail.com> wrote:
>> TL;DR: During the six next months, we will follow pull requests (PR)
>> posted on the github mirror of the OCaml distribution, as an
>> alternative to the mantis bugtracker.
> We now also have a GitHub mirror of the OCaml manual:
>
> https://github.com/ocaml/ocamldoc/
>
> Could we please extend the experiment to include pull requests to the
> manual as well as to the main source tree? There have been a few pull
> requests recently that will need corresponding updates to the
> documentation. It'd be useful to give source and documentation
> changes the same visibility.
>
next prev parent reply other threads:[~2014-04-08 12:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 11:34 [Caml-list] " Gabriel Scherer
2014-03-25 16:40 ` Anil Madhavapeddy
2014-03-25 21:34 ` [Caml-list] [ocaml-platform] " Yotam Barnoy
2014-03-26 9:00 ` François Bobot
2014-03-26 9:12 ` Louis Gesbert
2014-03-26 9:37 ` Anil Madhavapeddy
2014-04-08 12:37 ` Jeremy Yallop
2014-04-08 12:59 ` Jacques-Pascal Deplaix [this message]
2014-04-08 13:35 ` Gabriel Scherer
2014-04-08 13:39 ` Anil Madhavapeddy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5343F2A1.8020209@gmail.com \
--to=jp.deplaix@gmail.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=platform@lists.ocaml.org \
--cc=yallop@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox