[LLVMdev] LLVM maintainers, code reviews

Chandler Carruth chandlerc at google.com
Thu Nov 11 00:34:22 PST 2010


FYI, several developers already use Rietveld for code reviews:
http://codereview.appspot.com/

I'd rather focus on one that we already have a base of familiarity with if
we're going to use something more than email.

On Wed, Nov 10, 2010 at 8:56 AM, Bjorn Reese <breese at mail1.stofanet.dk>wrote:

> On 2010-11-10 12:58, Renato Golin wrote:
>
> > In a nutshell, the design decisions should be communicated more
> > effectively, and a Wiki is a great place to start. Peer reviewers
> > should communicate via the Wiki, so patchers could learn and plan
> > before the next iteration and reduce the cost for everybody.
>
> You may consider using a review tool rather than (or in addition to)
> llvm-commit. For instance:
>
>   http://www.reviewboard.org/
>
> With this tool you can assign review responsibility of certain parts of
> the code to different reviewers, so if somebody submits a patch of some
> source code files, the responsible reviewers will automatically get a
> review request in their inbox.
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101111/5010663e/attachment.html>


More information about the llvm-dev mailing list