Lines Matching refs:review
67 button. Then select a review. Remember to be positive and add value with every
68 review comment.
160 We use git for almost everything. Most projects in OpenBMC use Gerrit to review
178 - Work at most a few days before seeking review.
179 - Commit and review header files before writing code.
180 - Commit and review each implementation module separately.
184 push commits which are based on your change still in review. However, when
214 whitespace changes - this makes review unnecessarily difficult.
323 [Change-Ids](https://gerrit-review.googlesource.com/Documentation/user-changeid.html)
324 to identify commits that belong to the same review. Configure your git
342 [Gerrit documentation](https://gerrit-review.googlesource.com/Documentation/intro-user.html#topics).
344 Gerrit will show you the URL link to your review. You can also find your reviews
348 Invite reviewers to review your changes. Each OpenBMC repository has an `OWNERS`
356 The review results in the proposed change being accepted, rejected for rework,
358 so Gerrit handles the update as a new patch of the same review.
438 deep review queues already of patches which have been waiting longer than yours.
439 Do everything you can to make it easy for the reviewer to review your