X-Git-Url: https://git.karo-electronics.de/?a=blobdiff_plain;f=Documentation%2FSubmittingPatches;h=689e2371095cc5dfea9927120009341f369159aa;hb=6f576d57f1fa0d6026b495d8746d56d949989161;hp=72651f788f4e3536149ef5e7ddfbed96a8f14d2f;hpb=6b46362c0ea472b174c336786fd406c504326ad4;p=mv-sheeva.git

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 72651f788f4..689e2371095 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -98,6 +98,17 @@ system, git, as a "commit log".  See #15, below.
 If your description starts to get long, that's a sign that you probably
 need to split up your patch.  See #3, next.
 
+When you submit or resubmit a patch or patch series, include the
+complete patch description and justification for it.  Don't just
+say that this is version N of the patch (series).  Don't expect the
+patch merger to refer back to earlier patch versions or referenced
+URLs to find the patch description and put that into the patch.
+I.e., the patch (series) and its description should be self-contained.
+This benefits both the patch merger(s) and reviewers.  Some reviewers
+probably didn't even receive earlier versions of the patch.
+
+If the patch fixes a logged bug entry, refer to that bug entry by
+number and URL.
 
 
 3) Separate your changes.