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 mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 90B827EE99 for ; Sat, 11 Jan 2014 16:41:55 +0100 (CET) Received-SPF: Neutral (mail2-smtp-roc.national.inria.fr: domain of simon.cruanes.2007@m4x.org does not assert whether or not 129.104.30.34 is permitted sender) identity=pra; client-ip=129.104.30.34; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="SRS0=dSmV=WR=m4x.org=simon.cruanes.2007@bounces.m4x.org"; x-sender="simon.cruanes.2007@m4x.org"; x-conformance=sidf_compatible; x-record-type="spf2.0" Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of SRS0=dSmV=WR=m4x.org=simon.cruanes.2007@bounces.m4x.org designates 129.104.30.34 as permitted sender) identity=mailfrom; client-ip=129.104.30.34; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="SRS0=dSmV=WR=m4x.org=simon.cruanes.2007@bounces.m4x.org"; x-sender="SRS0=dSmV=WR=m4x.org=simon.cruanes.2007@bounces.m4x.org"; x-conformance=sidf_compatible; x-record-type="spf2.0" Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of postmaster@mx1.polytechnique.org designates 129.104.30.34 as permitted sender) identity=helo; client-ip=129.104.30.34; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="SRS0=dSmV=WR=m4x.org=simon.cruanes.2007@bounces.m4x.org"; x-sender="postmaster@mx1.polytechnique.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah0DACRl0VKBaB4inGdsb2JhbABZg0ODVLEXhlkWDgEBAQEBCBQJPIImAQEEI0sLEAshIQICDwUoIYgXBAmoXppkFxaOGQcBAYNFNYETBJgWgTGUE4FnCRc X-IPAS-Result: Ah0DACRl0VKBaB4inGdsb2JhbABZg0ODVLEXhlkWDgEBAQEBCBQJPIImAQEEI0sLEAshIQICDwUoIYgXBAmoXppkFxaOGQcBAYNFNYETBJgWgTGUE4FnCRc X-IronPort-AV: E=Sophos;i="4.95,643,1384297200"; d="scan'208";a="52803747" Received: from mx1.polytechnique.org ([129.104.30.34]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 11 Jan 2014 16:41:55 +0100 Received: from lenat (mna75-4-82-225-76-110.fbx.proxad.net [82.225.76.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 2BC1514008FC0; Sat, 11 Jan 2014 16:41:54 +0100 (CET) Date: Sat, 11 Jan 2014 16:41:47 +0100 From: Simon Cruanes To: Adrien Nader Cc: "caml-list@inria.fr" Message-ID: <20140111154146.GA976@lenat> References: <20140111152357.GB28133@notk.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: <20140111152357.GB28133@notk.org> User-Agent: Mutt/1.5.22 (2013-10-16) X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Sat Jan 11 16:41:54 2014 +0100 (CET)) X-Spam-Flag: No, tests=bogofilter, spamicity=0.003565, queueID=5DE7B1407CB8E X-Org-Mail: simon.cruanes.2007@polytechnique.org Subject: Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Le Sat, 11 Jan 2014, Adrien Nader a =C3=A9crit : > Hi, >=20 > (and sorry for the mail sent a few minutes ago :) ) >=20 > I'd like to know what people think about having a mailing-list for > reviews and tests of patches to the compiler and tools around it. >=20 > The idea is to do something similar to the kernel mailing-list. I mostly > like mantis and it is possible to attach files but it becomes fairly > unreadable after a while. The audience is also mostly limited to people > who are subscribed to the bug report. I hope this reduces the work and > burden of reviewers and especially commiters. >=20 > The goal is not to replace patches on mantis and you shouldn't believe > this has been blessed by the core development team (nor mentionned to > them actually). Instead, I hope this helps do quicker (and smaller?) > iteration of patches. >=20 > One example where I believe this would be useful is for the > cross-compilation patches I've started getting upstreamed around one > year ago. There are still many patchs which touch many files and > definitely need tests on platforms I don't usually run. >=20 > Another case is for patches which touch bits of the compiler almost > no-one is familiar with; I think this could help get more input. >=20 > Rules would be similar to http://linux.yyz.us/patch-format.html but less > strict (that is also mostly something to begin with). > In addition, there should be no specific reviewer or set of reviewers > for a given component; it is also known, acknowledged and perfectly fine > that the available time of reviewers varies. In practice this means you > should not refrain from commenting on a patch because someone else > usually handles a given topic. >=20 > Of course, this requires two things: a bit of infrastructure (I hear > it's much easier to create mailing-lists on ocaml.org than on inria's > servers), and people (i.e. you). Anyone interested and willing to > participate? The idea is nice. I don't know the compiler's internals and would certainly be interested in being familiar with them. Is a new mailing list necessary - do you envision massive traffic on the list - or could the current ocaml list, which is usually quite quiet, be used for compiler discussions? The parallel with the recent suggestion to host wikis on ocaml.org to centralize information about how to do parallelism (or other similar topics regarding the high-level use of OCaml) may be interesting. Would a small-ish wiki about the compiler and compiler's hacking be useful? Can a mailing-list play the same role as a wiki? Cheers, --=20 Simon --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCgAGBQJS0WY6AAoJEErAHQhJqmK2T44QAMTv3STbKsmW8+i6WDpW/nHY cMSPbs0tTqfbj1VfahmIP4ZxKYEGCFj2c0T8zGV1qZots9NnTRH6WUjFTZTzkASq jtUFAGS3FMHoY3rNu+ocEaoKQ+0LjHUwmCxNjWmgsp5v+zOCER1t+j5TKvm+fk1u AXvwfwh0MRpvQV2ezQ3BqsPf0UVIhR/uVvEOfO7fFRjnkDPQKIapRdOX2C1OJ5hk 9QGBEWgiAVNxJpOSzjozskLXDc23+uz+1+/T9ACnZSJc4ubYjVRj8G9z+f+xgVJq Y5+g93plxOrWUt4XS4hCAI1SSNjQOcHOYmRM+QCyxKBkTQCOvg7+6/13FjgvPrBE Lj0AZZUAUwTxpIXExaUdPY86QoZHYwP4CCObL0VfLnOw1izZMmfURecpaF8noUjo 0dlg76GIcFjy4/X6ww+mFSdwbd3dqunLHcXj2DZGa5MeDJevvWLvdJJDhqsGUtmL oSNUHw8KZwCk0OWihsA5d/lYDHVXwogdYWgXLnsPep1+WQsvwpceOmkbswatVBaR BLmrKqzk1g/NCB5TbqliiPAKv2wmGRjTpGMvrcqxY5FpaoYz8mndtwwxszp1KKa0 VvWrZnC5+iWT+pjqJ7+zSVWFCpCwFe37/5TU/qvsZuXcF35+Yv8hLWJC8U0ZhgS2 vVL2uvmJ2XanJFB0IDbc =O7G2 -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs--