Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list

[Kakadu <kakadu.hafanana@gmail.com>]

Qt Gerrit [1] is the most fascinating review system I have ever seen.
Everybody can push commits and add reviewers for it. CI is enabled for
every change. Any chance that OCaml will  have the same available?

[1] https://codereview.qt-project.org/#change,75024

Cheers,
Kakadu

On Mon, Jan 13, 2014 at 1:43 PM, Thomas Refis <thomas.refis@gmail.com> wrote:
> 2014/1/13 Gabriel Scherer <gabriel.scherer@gmail.com>:
>> On Mon, Jan 13, 2014 at 12:14 PM, Daniel Bünzli
>> <daniel.buenzli@erratique.ch> wrote:
>>> It's not only easy to browse, it's *great* to browse: all the web-based mailing list archives I interact with are not even able to follow a thread running across two month. I really feel we're in 2014.
>>
>> This is a bit too snarky for me to guess what you want.
>
> I'd have thought that part was pretty obvious. If the discussion
> starts on the 28th of a month, and is continued the next month. The
> "sympa" interface gives you no easy way to follow the thread. You need
> to "select" the second month, and find the thread again.
>
>> I'm already doing a few reviews on mantis, and occasionally uses the
>> github in-patch-commenting interface when people send a link to a
>> github-hosted patch (eg. http://caml.inria.fr/mantis/view.php?id=6274
>> ).
>
> Since we're talking about it: I was a bit confused with that review.
> Although *I* find the github interface nicer than mantis and the "in
> patch comments" really useful, I didn't know whether I should answer
> your comments on github or on mantis, and people on mantis might not
> see the comments you did.
> So I'm not sure that's really a good approach. (But of course that
> particular patch was about ocamldoc, which no one really cares about,
> so I guess that's ok)
>
> Thomas.
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs