path: root/Documentation/SubmittingPatches
diff options
authorJosh Triplett <>2014-04-03 14:48:29 -0700
committerLinus Torvalds <>2014-04-03 16:21:06 -0700
commit9547c706d279392d53922c0f9d57a0b37a4dfcdc (patch)
treeb421e9ae444fab550c1f0f9d1ff507c0ea31cfa5 /Documentation/SubmittingPatches
parent74a475acea49459721ae4b062d3da68c74259009 (diff)
SubmittingPatches: add recommendation for mailing list references
SubmittingPatches already mentions referencing bugs fixed by a commit, but doesn't mention citing relevant mailing list discussions. Add a note to that effect, along with a recommendation to use the redirector. Portions based on text from git's SubmittingPatches. Signed-off-by: Josh Triplett <> Acked-by: Borislav Petkov <> Cc: Rob Landley <> Cc: Randy Dunlap <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
Diffstat (limited to 'Documentation/SubmittingPatches')
1 files changed, 9 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index c74e73c37dcc..53e6590263a1 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -112,7 +112,15 @@ to do frotz", as if you are giving orders to the codebase to change
its behaviour.
If the patch fixes a logged bug entry, refer to that bug entry by
-number and URL.
+number and URL. If the patch follows from a mailing list discussion,
+give a URL to the mailing list archive; use the
+redirector with a Message-Id, to ensure that the links cannot become
+However, try to make your explanation understandable without external
+resources. In addition to giving a URL to a mailing list archive or
+bug, summarize the relevant points of the discussion that led to the
+patch as submitted.
If you want to refer to a specific commit, don't just refer to the
SHA-1 ID of the commit. Please also include the oneline summary of