From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 49BE57EC6E for ; Tue, 14 Jan 2014 00:09:40 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of adrien@notk.org) identity=pra; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of adrien@notk.org designates 91.121.71.147 as permitted sender) identity=mailfrom; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@nautica.notk.org) identity=helo; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="postmaster@nautica.notk.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AikFAMZx1FJbeUeT/2dsb2JhbABagwuDOlK2doEVFnSCJQEBAQQjDwE7GwsYAgIFEw4CAg8FGDGIG6onmwkXgSmNZYJvNYETBJgWAZIVgy47 X-IPAS-Result: AikFAMZx1FJbeUeT/2dsb2JhbABagwuDOlK2doEVFnSCJQEBAQQjDwE7GwsYAgIFEw4CAg8FGDGIG6onmwkXgSmNZYJvNYETBJgWAZIVgy47 X-IronPort-AV: E=Sophos;i="4.95,655,1384297200"; d="scan'208";a="44666467" Received: from nautica.notk.org ([91.121.71.147]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 14 Jan 2014 00:09:39 +0100 Received: by nautica.notk.org (Postfix, from userid 1003) id C3D72C009; Tue, 14 Jan 2014 00:09:38 +0100 (CET) Date: Tue, 14 Jan 2014 00:09:38 +0100 From: Adrien Nader To: caml users Message-ID: <20140113230938.GA8515@notk.org> References: <20140111152357.GB28133@notk.org> <20140111154146.GA976@lenat> <20140113090444.GA8904@notk.org> <52D3B71B.40802@cea.fr> <20140113223021.GA30935@notk.org> <20140113223916.GE976@lenat> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20140113223916.GE976@lenat> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list 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