* [Qemu-devel] Re: Proposal: Improving patch tracking and review using Rietveld
[not found] <AANLkTimkJA8OGjrhwsrzbm6W+NZXKeUnG7EYEHVZ+xen@mail.gmail.com>
@ 2011-01-27 10:25 ` Paolo Bonzini
0 siblings, 0 replies; only message in thread
From: Paolo Bonzini @ 2011-01-27 10:25 UTC (permalink / raw)
To: Diego Novillo; +Cc: gcc, Jeffrey Yasskin, Richard Earnshaw, qemu-devel
On 01/26/2011 08:56 PM, Diego Novillo wrote:
> At Google we use a code review tool which was open sourced a couple of
> years ago: Rietveld
> (http://code.google.com/appengine/articles/rietveld.html).
>
> The best way of thinking about it is "bugzilla for patches". The
> system creates an entry for every patch submitted, provides a web tool
> for manipulating the patch (comments, different views of the diff,
> highlighting, etc) and it also has an email gateway.
>
> We have discussed patch tracking mechanisms in the past, and none so
> far has taken hold. The reason why I like Rietveld is that it doesn't
> really matter whether we all switch to using it at once:
>
> 1- Rietveld always send the patch sent to it to gcc-patches@ (provided
> the submitter added gcc-patches to the CC list).
> 2- The whole trail of discussion on the patch also get sent to
> gcc-patches and everyone else is CC'd in it.
> 3- Reviewers do not need to use the web tool to reply to the patch.
> One can simply respond to the e-mail, and it will get added to the
> patch discussion trail.
How does this work WRT multiple revisions of the same patch?
I am taking the liberty of CCing qemu-devel since I forwarded your
message there.
Paolo
^ permalink raw reply [flat|nested] only message in thread