fixup! [docs] Update docs on code-review process

Revert changes in llvm/docs/Contributing.rst, update llvm/docs/CodeReview.rst instead.

Author: banach-space

llvm/docs/CodeReview.rst

@@ -150,14 +150,18 @@ almost always associated with a message containing the text "LGTM" (which
 stands for Looks Good To Me). Only approval from a single reviewer is required.
 
 When providing an unqualified LGTM (approval to commit), it is the
-responsibility of the reviewer to have reviewed all of the discussion and
+responsibility of the reviewer to have reviewed all of the prior discussion and
 feedback from all reviewers ensuring that all feedback has been addressed and
 that all other reviewers will almost surely be satisfied with the patch being
 approved. If unsure, the reviewer should provide a qualified approval, (e.g.,
 "LGTM, but please wait for @someone, @someone_else"). You may also do this if
 you are fairly certain that a particular community member will wish to review,
 even if that person hasn't done so yet.
 
+If new comments are posted after the patch has been approved (but not yet
+merged), these need to be addressed and all new changes have to be reviewed and
+approved by a reviewer.
+
 Note that, if a reviewer has requested a particular community member to review,
 and after a week that community member has yet to respond, feel free to ping
 the patch (which literally means submitting a comment on the patch with the

llvm/docs/Contributing.rst

@@ -105,16 +105,9 @@ get the attention of potential reviewers by CC'ing them in a comment -- just
 A reviewer may request changes or ask questions during the review. If you are
 uncertain on how to provide test cases, documentation, etc., feel free to ask
 for guidance during the review. Please address the feedback and re-post an
-updated version of your patch. This cycle continues until all requests and
-comments have been addressed and the reviewer accepts the patch with a `Looks
-good to me` or `LGTM`. With multiple active reviewers (i.e. reviewers who left
-comments), it is good practice to seek `LGTM` from all of them. Alternatively, 
-when e.g. some reviewers go radio silent and you are blocked:
-* any reviewer can confirm that all comments from other reviewers have been
-  addressed and the change is ready to land, or
-* if you decide not to wait for explicit `LGTM` from other reviewers, please
-  leave a short justification.
-Once a change has been approved, it can be committed. If you do not have commit
+updated version of your patch. This cycle continues until all requests and comments
+have been addressed and a reviewer accepts the patch with a `Looks good to me` or `LGTM`.
+Once that is done the change can be committed. If you do not have commit
 access, please let people know during the review and someone should commit it
 on your behalf.