[PATCH] Documentation: -stable rules: upstream commit ID requirementreworded

[Stefan Richter]

It is a hard requirement to include the upstream commit ID in the
changelog of a -stable submission, not just a courtesy to the stable
team.  This concerns only mail submission though, which is no longer
the only way into stable.  (Also, fix a double "the".)

Signed-off-by: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
---
 Documentation/stable_kernel_rules.txt |    9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

Index: b/Documentation/stable_kernel_rules.txt
===================================================================
--- a/Documentation/stable_kernel_rules.txt
+++ b/Documentation/stable_kernel_rules.txt
@@ -18,16 +18,15 @@ Rules on what kind of patches are accept
  - It cannot contain any "trivial" fixes in it (spelling changes,
    whitespace cleanups, etc).
  - It must follow the Documentation/SubmittingPatches rules.
- - It or an equivalent fix must already exist in Linus' tree.  Quote the
-   respective commit ID in Linus' tree in your patch submission to -stable.
+ - It or an equivalent fix must already exist in Linus' tree (upstream).
 
 
 Procedure for submitting patches to the -stable tree:
 
  - Send the patch, after verifying that it follows the above rules, to
-   stable@xxxxxxxxxxx
- - To have the patch automatically included in the stable tree, add the
-   the tag
+   stable@xxxxxxxxxxx  You must note the upstream commit ID in the changelog
+   of your submission.
+ - To have the patch automatically included in the stable tree, add the tag
      Cc: stable@xxxxxxxxxx
    in the sign-off area. Once the patch is merged it will be applied to
    the stable tree without anything else needing to be done by the author

-- 
Stefan Richter
-=====-==-=- -=-- ----=
http://arcgraph.de/sr/

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/