[Buildroot] [RFC] Gerrit for BR

Yegor Yefremov yegor_sub1 at visionsystems.de
Fri Oct 21 10:17:19 UTC 2011

Am 21.10.2011 09:49, schrieb Peter Korsgaard:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at free-electrons.com> writes:
> Hi,
>  >> What do you think about using Gerrit
>  >> (http://code.google.com/p/gerrit/) for Buildroot? Many OSS projects
>  >> seem to switch to this system.
>  Thomas> How does it compare to patchwork (http://patchwork.ozlabs.org/)
>  Thomas> ?  Patchwork works in relation to a mailing-list, from which it
>  Thomas> automatically picks up patches and related review comments, and
>  Thomas> it allows maintainers to track which patches have been
>  Thomas> applied/not applied.
>  Thomas> How does Gerrit work in that respect?
> I don't have any hands on experience (but I am following the openocd
> list, so I see it used), and my initial feeling is that something like
> patchwork would fit better our current way of working.
> But that's just an initial feeling, let's discuss at ELC and/or here on
> the list.

Peter, you just mentioned yourself, that you're following openocd list. Please see this thread for pros contra etc.

As far as I understand Gerrit integrates very good with Git and when used properly and by all contributors, you'll have all the patches in one place. The patches can be then commented online and you'll also get history for reworked patches. As soon as patches are verified, maintainer (you :-) ) can merge them with one click. These were the benefits Gerrit would bring Buidroot community. I think such approach makes sense, since lots of patches will be sent almost every day.

And as far as I understand from the openocd list thread mentioned above, patchwork still requires more handwork from maintainer than Gerrit.


More information about the buildroot mailing list