Home | History | Annotate | Download | only in docs

Lines Matching full:review

77 When making a patch for review, the goal is to make it as easy for the reviewer
110 .. _code review:
115 LLVM has a code review policy. Code review is one way to increase the quality of
128 all necessary review-related changes.
130 #. Code review can be an iterative process, which continues until the patch is
134 reviewees. If someone is kind enough to review your code, you should return the
135 favor for someone else. Note that anyone is welcome to review and give feedback
138 There is a web based code review tool that can optionally be used
146 of code review plus post-commit review for trusted maintainers. Having both is
149 review when they are confident they are right.
153 someone else will review it, allowing the patch to go unreviewed. To solve this
162 review a piece of code, and we welcome code review from anyone who is
300 In any case, your changes are still subject to `code review`_ (either before or
302 encouraged to review other peoples' patches as well, but you aren't required
348 extremely difficult to `code review`_.
374 (into a logical progression), simplifies code review and reduces the chance
380 "obvious" and can be committed without review. Once the new API is in place