Lines Matching refs:review

25 3. Should be a reasonable size to review.  Giant patches are unlikely to get reviewed quickly.
61    * Wait for the bots to report the result on the code review page. The bot results should be
122 1. Go to [https://chromium-review.googlesource.com/new-password][CR-passwd]
126    * Visit [https://chromium-review.googlesource.com/#/settings][CR-settings] and check the "Full
131      CL with a particular review, and track dependencies between commits.
133      [https://chromium-review.googlesource.com/tools/hooks/commit-msg][commit-msg-hook] and copy
137      not currently be used with changes intended for review.
139 [CR-passwd]: https://chromium-review.googlesource.com/new-password
140 [CR-settings]: https://chromium-review.googlesource.com/#/settings
141 [commit-msg-hook]: https://chromium-review.googlesource.com/tools/hooks/commit-msg
163    * Take a moment to perform a self-review of your code. Gerrit's viewer makes it easy to see
166      you're requesting a review!
168    * Project members and others will review your code as described in the
181 [ANGLE-Gerrit]: https://chromium-review.googlesource.com/q/project:angle/angle
185 When your CL is ready to review, you can use the "Find Owners" button in
223 [RevertCL]: https://chromium-review.googlesource.com/c/chromium/src/+/2453504
240 [RelandCL]: https://chromium-review.googlesource.com/c/angle/angle/+/2197735
241 [RelandCLDiff]: https://chromium-review.googlesource.com/c/angle/angle/+/2197735/1..3
251 request committer status from a core ANGLE team member via email or code review.  Chromium