caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list
Date: Tue, 14 Jan 2014 00:09:38 +0100	[thread overview]
Message-ID: <20140113230938.GA8515@notk.org> (raw)
In-Reply-To: <20140113223916.GE976@lenat>

On Mon, Jan 13, 2014, Simon Cruanes wrote:
> Le Mon, 13 Jan 2014, Adrien Nader a écrit :
> 
> > Reducing reviewer work and/or having more reviewers was the actual goal
> > behind my proposal.
> > Another core aspect is that setting up a mailing-list and putting up a
> > "howto contribute" page takes a few minutes of work unlike migrations of
> > whole systems or the use of forges(*).
> > 
> > I was also not thinking of replacing patches and reviews on mantis, more
> > having an additional tool to conduct code review although, of course, I
> > would prefer a single place for that. In any case, having something
> > agreed upon and documented is probably what matters most.
> > 
> > On a personal note, I also prefer getting fed with emails for which I
> > will use a decent client with an editor I enjoy rather than a web
> > browser (especially when there's flash on the pages).
> 
> So, what's actually needed and sufficient, you believe, is a proper
> mailing list manager, which provides a friendly interface to navigate
> through the archive?

Well, I believe a mailing-list would be suited to code review. I don't
even mind that archives require a minor hoop to navigate in long
messages since that wouldn't be the main way it is used. I can't tell if
it's needed or sufficient though.

-- 
Adrien Nader

  reply	other threads:[~2014-01-13 23:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 15:23 Adrien Nader
2014-01-11 15:41 ` Simon Cruanes
2014-01-13  9:04   ` Adrien Nader
2014-01-13  9:51     ` François Bobot
2014-01-13 10:27       ` Gabriel Scherer
2014-01-13 11:14         ` Daniel Bünzli
2014-01-13 13:26           ` Gabriel Scherer
2014-01-13 13:43             ` Thomas Refis
2014-01-13 13:51               ` Gabriel Scherer
2014-01-13 13:57               ` Simon Cruanes
2014-01-13 15:03                 ` Török Edwin
2014-01-13 13:58               ` Kakadu
2014-02-17 22:55                 ` Richard W.M. Jones
2014-01-13 13:57             ` Daniel Bünzli
2014-01-13 22:30             ` Adrien Nader
2014-01-13 22:39               ` Simon Cruanes
2014-01-13 23:09                 ` Adrien Nader [this message]
2014-01-14 11:13             ` Gabriel Kerneis
2014-01-14 13:23               ` François Bobot
2014-01-14 13:27                 ` Thomas Gazagnaire
2014-01-14 14:06                   ` Markus Mottl
2014-01-14 14:12                     ` Simon Cruanes
2014-01-14 14:55                       ` Amir Chaudhry
2014-01-14 15:09                       ` François Bobot
2014-01-14 15:11                         ` Anil Madhavapeddy
2014-01-13 16:42         ` Yotam Barnoy

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=20140113230938.GA8515@notk.org \
    --to=adrien@notk.org \
    --cc=caml-list@inria.fr \
    /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).