diff options
-rw-r--r-- | Documentation/SubmittingPatches | 10 |
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 | |||
112 | its behaviour. | 112 | its behaviour. |
113 | 113 | ||
114 | If the patch fixes a logged bug entry, refer to that bug entry by | 114 | If the patch fixes a logged bug entry, refer to that bug entry by |
115 | number and URL. | 115 | number and URL. If the patch follows from a mailing list discussion, |
116 | give a URL to the mailing list archive; use the https://lkml.kernel.org/ | ||
117 | redirector with a Message-Id, to ensure that the links cannot become | ||
118 | stale. | ||
119 | |||
120 | However, try to make your explanation understandable without external | ||
121 | resources. In addition to giving a URL to a mailing list archive or | ||
122 | bug, summarize the relevant points of the discussion that led to the | ||
123 | patch as submitted. | ||
116 | 124 | ||
117 | If you want to refer to a specific commit, don't just refer to the | 125 | If you want to refer to a specific commit, don't just refer to the |
118 | SHA-1 ID of the commit. Please also include the oneline summary of | 126 | SHA-1 ID of the commit. Please also include the oneline summary of |