Doesnt email run the risk of a patch slipping through the cracks?
On Tue, Apr 16, 2013 at 9:02 PM, Deepak Saxena <dsax...@linaro.org> wrote: > On 16 April 2013 07:06, Jonathan Aquilina <eagles051...@gmail.com> wrote: > > Wouldnt all of them benefit in a way from it? > > My take on this is that one of the goals of Linaro's assignee process > is to teach folks how to work in the open source community and than > take that knowledge back to internal teams. This means we should use > communication methods and tools that are native to the upstream > communities we interact with and in the case of the kernel, this means > that code review should be done via email lists. > > ~Deepak > > > > > > > On Tue, Apr 16, 2013 at 4:04 PM, Nicolas Dechesne > > <nicolas.deche...@linaro.org> wrote: > >> > >> On Tue, Apr 16, 2013 at 3:59 PM, Jonathan Aquilina > >> <eagles051...@gmail.com> wrote: > >> > Have you guys considered gerrit code review for patches? as well as > >> > setting > >> > up build bots to test build the patches? > >> > >> which projects at Linaro you have in mind for this request? it's > >> already being used for Android 'stuff', see > >> > >> http://review.android.git.linaro.org/ > > > > > > > > > > -- > > Jonathan Aquilina > > > > _______________________________________________ > > linaro-dev mailing list > > linaro-dev@lists.linaro.org > > http://lists.linaro.org/mailman/listinfo/linaro-dev > > > > > > -- > Deepak Saxena - Kernel Working Group Lead > Linaro.org | Open source software for ARM SoCs > Follow Linaro: http://www.facebook.com/pages/Linaro > -- Jonathan Aquilina
_______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
