caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Joel Reymont <joelr1@gmail.com>
To: Markus Mottl <markus.mottl@gmail.com>
Cc: "Richard W.M. Jones" <rich@annexia.org>,
	Benedikt Meurer <benedikt.meurer@googlemail.com>,
	 caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: Anyone using Benedikt Meurer's new ARM code generator?
Date: Tue, 15 May 2012 19:28:27 +0100	[thread overview]
Message-ID: <CAOQwdX1h7NFgNLGYLKgjvQXTm9-heAw_RthgDRuKbn9XijLCZQ@mail.gmail.com> (raw)
In-Reply-To: <CAP_800rzjG8h58STH9um-Kec54dmsdqs2SCDwoKrx5=3-ePNLg@mail.gmail.com>

http://github.com

This would allow for documentation, etc. to be kept online and edited easily.

It would also allow for documented and well-presented pull requests
with patches.

On Tue, May 15, 2012 at 7:10 PM, Markus Mottl <markus.mottl@gmail.com> wrote:
> On Tue, May 15, 2012 at 1:34 PM, Richard W.M. Jones <rich@annexia.org> wrote:
>> (why-oh-why doesn't OCaml use git!)
>
> It would indeed be awesome if the OCaml team considered switching to a
> modern, distributed VCS.  Both git and Mercurial are vastly superior
> to SVN.  Conversion tools also make it trivial to switch.  This could
> really boost community productivity for bug fixing and feature
> proposals.
>
> Regards,
> Markus
>
> --
> Markus Mottl        http://www.ocaml.info        markus.mottl@gmail.com
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>



-- 
--------------------------------------------------------------------------
AlgoKit: EasyLanguage trading strategies, on the server, w/ Rithmic R|API
---------------------+------------+---------------------------------------
http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont
---------------------+------------+---------------------------------------

  reply	other threads:[~2012-05-15 18:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 17:11 [Caml-list] " Richard W.M. Jones
2012-05-15 17:31 ` [Caml-list] " Benedikt Meurer
2012-05-15 17:34   ` Richard W.M. Jones
2012-05-15 18:10     ` Markus Mottl
2012-05-15 18:28       ` Joel Reymont [this message]
2012-05-15 19:05         ` Richard W.M. Jones
2012-05-15 19:22           ` Daniel Bünzli
2012-05-15 19:33           ` Ashish Agarwal
2012-05-15 19:48             ` Mehdi Dogguy
     [not found]   ` <20120515180143.GZ18947@annexia.org>
     [not found]     ` <6F6DA73D-36C7-43D8-A03A-7DDD066E6113@gmail.com>
     [not found]       ` <20120516154632.GA18383@annexia.org>
     [not found]         ` <C10EB135-966B-4996-8430-DC326D6B9F88@gmail.com>
2012-05-19  9:46           ` [Caml-list] segfault in camomile / gen_mappings.ml (was: Re: Anyone using Benedikt Meurer's new ARM code generator?) Richard W.M. Jones
2012-05-24 19:40             ` [Caml-list] " Benedikt Meurer
2012-05-25  9:01               ` Richard W.M. Jones

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=CAOQwdX1h7NFgNLGYLKgjvQXTm9-heAw_RthgDRuKbn9XijLCZQ@mail.gmail.com \
    --to=joelr1@gmail.com \
    --cc=benedikt.meurer@googlemail.com \
    --cc=caml-list@inria.fr \
    --cc=markus.mottl@gmail.com \
    --cc=rich@annexia.org \
    /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;
as well as URLs for NNTP newsgroup(s).