Lines Matching refs:comments

308 Respond to review comments
311 Your patch will almost certainly get comments from reviewers on ways in
313 respond to those comments; ignoring reviewers is a good way to get ignored in
314 return. You can simply reply to their emails to answer their comments. Review
315 comments or questions that do not lead to a code change should almost certainly
340 receive comments within a week or so; if that does not happen, make sure
454 provided such comments, you may optionally add a ``Cc:`` tag to the patch.
524 	     with the submitter's response to my comments.
600   - Any additional comments not suitable for the changelog.
639 comments (i.e., "v1, v2, v3"), or "RFC" to indicate a request for
640 comments.
682 One good use for the additional comments after the ``---`` marker is
691 Other comments relevant only to the moment or the maintainer, not
693 example of such comments might be ``patch changelogs`` which describe
709   V1 -> V2: Cleaned up coding style and addressed review comments