chromium/src
0
Fork 0
Code Activity

Add details to a section in docs/cl_respect.md.

Browse Source 
Change-Id: I9e5f5b9ee05cb3cdc4ad6a5b06c5229fde5747ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4405152
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Auto-Submit: Kale Lettuce <kalettuce@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1127443}
This commit is contained in:
kalettuce
2023-04-06 23:02:55 +00:00
committed by Chromium LUCI CQ
parent 7e89329b64
commit dd7e8846ae
1 changed files with 4 additions and 2 deletions

6
docs/cl_respect.md

@ -98,8 +98,10 @@ though you may have addressed that comment in a new patchset, don't submit the
CL until you have their LGTM, unless the reviewer gave the OK to do so (e.g.
when the reviewer delegates the reviewing task to someone else). If you need to
land a CL urgently and one of your reviewers isn't available (e.g. OOO), submit
your CL, and send your reviewer a note to show that you've considered their
opinions & are willing to act on their additional comments in a followup CL.
your CL, and send your reviewer a note; in the note, be sure to include the
reason why you had to land the CL, and show that you've considered their
opinions & are ready to promptly act on their additional comments in a followup
CL.
#### What to do if it's going wrong