Searched refs:reviewer (Results 1 – 25 of 48) sorted by relevance
12
| /external/swiftshader/third_party/llvm-7.0/llvm/utils/Reviewing/ |
| D | find_interesting_reviews.py | 421 for reviewer, scores in matched_reviewers:
423 reviewer,
425 if reviewer not in reviewer2reviews_and_scores:
426 reviewer2reviews_and_scores[reviewer] = []
427 reviewer2reviews_and_scores[reviewer].append((review, scores))
430 for reviewer in sorted(reviewer2reviews_and_scores.keys()):
431 reviews_and_scores = reviewer2reviews_and_scores[reviewer]
434 reviewer, len(reviews_and_scores)))
499 for reviewer, nr_occurences in \
501 if reviewer not in reviewers2nr_lines_touched:
[all …]
|
| /external/v8/tools/release/ |
| D | auto_push.py | 78 "--reviewer", self._options.reviewer,
98 if not options.author or not options.reviewer: # pragma: no cover
|
| D | common_includes.py | 770 reviewer = None
771 if self._options.reviewer:
772 print "Using account %s for review." % self._options.reviewer
773 reviewer = self._options.reviewer
780 if not reviewer and not tbr_reviewer:
783 reviewer = self.ReadLine()
785 self.GitUpload(reviewer, self._options.author, self._options.force_upload,
|
| D | git_recipes.py | 208 def GitUpload(self, reviewer="", author="", force=False, cq=False, argument
214 if reviewer:
215 args += ["-r", Quoted(reviewer)]
|
| D | auto_roll.py | 155 message.append("TBR=%s" % self._options.reviewer)
208 if not options.author or not options.reviewer:
|
| D | create_release.py | 206 text += "\n\nTBR=%s" % self._options.reviewer
271 if not options.author or not options.reviewer:
|
| /external/skqp/site/dev/contrib/ |
| D | submit.md | 71 ### Find a reviewer
73 Ideally, the reviewer is someone who is familiar with the area of code you are
120 review and click **Reply**. Enter at least one reviewer's email address. Now
126 in the upper right. _Hint_: You can add -r reviewer@example.com --send-mail to
136 Code reviews are an important part of the engineering process. The reviewer will
142 You will likely get email back from the reviewer with comments. Fix these and
157 notification (it is helpful to tell the reviewer what you did with respect to
158 each of their comments). When the reviewer is happy with your patch, they will
|
| /external/skia/site/dev/contrib/ |
| D | submit.md | 71 ### Find a reviewer
73 Ideally, the reviewer is someone who is familiar with the area of code you are
120 review and click **Reply**. Enter at least one reviewer's email address. Now
126 in the upper right. _Hint_: You can add -r reviewer@example.com --send-mail to
136 Code reviews are an important part of the engineering process. The reviewer will
142 You will likely get email back from the reviewer with comments. Fix these and
157 notification (it is helpful to tell the reviewer what you did with respect to
158 each of their comments). When the reviewer is happy with your patch, they will
|
| /external/syzkaller/pkg/vcs/ |
| D | git_test.go | 28 Acked-by: Subsystem reviewer <Subsystem@reviewer.com>
|
| /external/clang/ |
| D | OWNERS | 5 # mailing list cannot be a reviewer yet
|
| /external/compiler-rt/ |
| D | OWNERS | 5 # mailing list cannot be a reviewer yet
|
| /external/grpc-grpc/ |
| D | OWNERS | 12 # be forced to rely on one reviewer, which would consequently
|
| D | CONTRIBUTING.md | 74 - Unless your PR is trivial, you should expect there will be reviewer comments
106 green signal will be provided by our testing infrastructure. The reviewer
|
| /external/skia/site/dev/chrome/ |
| D | index.md | 17 Sheriff, listed at the top of https://status.skia.org and as a reviewer
|
| /external/skqp/site/dev/chrome/ |
| D | index.md | 17 Sheriff, listed at the top of https://status.skia.org and as a reviewer
|
| /external/skia/site/user/ |
| D | issue-tracker.md | 24 [status.skia.org](https://status.skia.org) and as a reviewer on the roll CL.
|
| /external/skqp/site/user/ |
| D | issue-tracker.md | 24 [status.skia.org](https://status.skia.org) and as a reviewer on the roll CL.
|
| /external/deqp-deps/SPIRV-Tools/ |
| D | CONTRIBUTING.md | 67 The reviewer can either approve your PR or request changes. If changes are
71 Adding new commits makes it easier for the reviewer to see what has changed
77 After the PR has been reviewed it is the job of the reviewer to merge the PR.
|
| /external/swiftshader/third_party/SPIRV-Tools/ |
| D | CONTRIBUTING.md | 67 The reviewer can either approve your PR or request changes. If changes are
71 Adding new commits makes it easier for the reviewer to see what has changed
77 After the PR has been reviewed it is the job of the reviewer to merge the PR.
|
| /external/google-breakpad/ |
| D | README | 36 and select Publish+Mail, and enter in the code reviewer and CC
|
| /external/skia/ |
| D | PRESUBMIT.py | 393 for reviewer in cr.GetReviewers():
394 if reviewer in PUBLIC_API_OWNERS:
|
| /external/google-styleguide/docguide/ |
| D | best_practices.md | 33 docs fresh, and is also a good place to explain to your reviewer what you're
36 A good reviewer can at least insist that docstrings, header files, README.md
|
| /external/skqp/ |
| D | PRESUBMIT.py | 393 for reviewer in cr.GetReviewers():
394 if reviewer in PUBLIC_API_OWNERS:
|
| /external/googletest/googlemock/scripts/ |
| D | upload.py | 1306 for reviewer in options.reviewers.split(','):
1307 if "@" in reviewer and not reviewer.split("@")[1].count(".") == 1:
1308 ErrorExit("Invalid email address: %s" % reviewer)
|
| /external/google-breakpad/src/testing/gtest/scripts/ |
| D | upload.py | 1306 for reviewer in options.reviewers.split(','):
1307 if "@" in reviewer and not reviewer.split("@")[1].count(".") == 1:
1308 ErrorExit("Invalid email address: %s" % reviewer)
|
12