From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [80.91.229.2] (helo=ciao.gmane.org) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1K8Hgy-0002SD-6X for openembedded-devel@openembedded.org; Mon, 16 Jun 2008 18:36:29 +0200 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1K8HgF-000539-Dz for openembedded-devel@openembedded.org; Mon, 16 Jun 2008 16:35:43 +0000 Received: from ip-62-143-23-251.hsi.ish.de ([62.143.23.251]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 16 Jun 2008 16:35:43 +0000 Received: from no2spam by ip-62-143-23-251.hsi.ish.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 16 Jun 2008 16:35:43 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: openembedded-devel@openembedded.org From: Rolf Leggewie Date: Mon, 16 Jun 2008 18:35:35 +0200 Message-ID: References: <1213345201.13942.3.camel@dax.rpnet.com> <74d0deb30806130306tf5ca604t7238ab26d715e03@mail.gmail.com> Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip-62-143-23-251.hsi.ish.de User-Agent: Thunderbird 2.0.0.14 (X11/20080505) In-Reply-To: Sender: news Subject: Re: Switching SCM to git and commit/review policy X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.10 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2008 16:36:31 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Koen Kooi wrote: > That won't work, since people will 'accidentally' misread the list to > avoid review. That implies ill-will. I don't agree with that assumption. I'd also assume that somebody who misread the list (accidentally or otherwise) and who then actually breaks something will get a powerful reminder ;-) Repeat offenders should also be easy to spot. We should not reject a white/blacklist prematurely. As far as getting maintainers involved, I agree that probably this will be a difficult part since it can become complicated quickly (too many things to check before making a commit)