On 18 May 2012 01:14, Peter Hutterer <[email protected]> wrote: > On Thu, May 17, 2012 at 10:39:55AM +0200, Ernst Sjöstrand wrote: >> Hi, >> >> (sorry for jumping in from the outside and breaking the thread!) >> >> I read about this problem and wanted to offer a suggestion! >> >> What if you set up a Gerrit server for git.freedesktop.org? That's the >> tool the Android OpenSource project uses among other things: >> https://android-review.googlesource.com/ >> Perhaps if it was easier to contribute to reviewing code, more people >> would do it more often? > >> It's also a very nice tool I have to say, I use it every day at work. >> It's easy to integrate with automatic >> testing of patchsets before they're submitted to the repository for example. > > tbh I doubt what we have is a tool problem. Patches are sent to the list and > can be reviewed quite easily there (for subscribers, anyway). The issue we > have is manpower and, more importantly, manpower of people with enough > knowledge to judge whether a patchset has side-effects beyond the obvious. > > in the end, such patches tend fall on the shoulders of a few and adding > another tool that they have to check will increase, not decrease, the > workload for those.
tbh using a mailing list for that looks very impractical. - patches get missed completely - there is no track of what is related to what (as in the part of the same patchset or new revision of the same patchset) - you get a lots of list noise due to patches being sent one by one Thanks Michal _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
