Merge branch 'jc/doc-final-resend'

Update developer doc.

* jc/doc-final-resend:
  SubmittingPatches: clarify the purpose of the final resend

diff --cc Documentation/SubmittingPatches
index 3bf2147787acc5cc0473a3e78c2fe47f36c4a6bb,87089654ae41a48ff74324991dcfc0f8ffdd9a9f..d12094bac5f46a3d8df1aee0b380e563a51dad47
--- 1/Documentation/SubmittingPatches
--- 2/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@@ -295,17 -297,20 +297,17 @@@ instead left the review to trusted othe
  
  Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and
  `Tested-by:` lines as necessary to credit people who helped your
- patch.
+ patch, and "cc:" them when sending such a final version for inclusion.
  
  [[sign-off]]
 -=== Certify your work by adding your "Signed-off-by: " line
 +=== Certify your work by adding your `Signed-off-by` trailer
  
 -To improve tracking of who did what, we've borrowed the
 -"sign-off" procedure from the Linux kernel project on patches
 -that are being emailed around.  Although core Git is a lot
 -smaller project it is a good discipline to follow it.
 +To improve tracking of who did what, we ask you to certify that you
 +wrote the patch or have the right to pass it on under the same license
 +as ours, by "signing off" your patch.  Without sign-off, we cannot
 +accept your patches.
  
 -The sign-off is a simple line at the end of the explanation for
 -the patch, which certifies that you wrote it or otherwise have
 -the right to pass it on as an open-source patch.  The rules are
 -pretty simple: if you can certify the below D-C-O:
 +If you can certify the below D-C-O:
  
  [[dco]]
  .Developer's Certificate of Origin 1.1