Lines Matching full:they

29 preserve CCs and keep non-subscribers in the loop on the threads they
92 unrelated to the bug they're chasing.) Put documentation first, not
166 for fixing this bug" (they can go below the ``---`` line in the email so
167 they don't go into the final commit message). Make sure the body of the
306 Send patches inline so they are easy to reply to with review comments.
328 Patches are easier to find if they start a new top-level thread, rather
364 When reviewers don't know your goal at the start of their review, they
366 series, because they do not have enough context yet at that point of
372 entire series; potential reviewers know what files they are interested
373 in, and they need an easy way determine if your series touches them.
435 process before they are accepted. This will often mean a series will
505 they're looking at the most recent version. (The first version of a
549 patches with a Reviewed-by tag, stating that they are happy with that
590 area of code will send notification to the list that they are including
611 everyone submitted more patches than they reviewed, we would have a