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 https://lkml.kernel.org/ redirector. Portions based on text from git's SubmittingPatches. Signed-off-by: Josh Triplett <josh@joshtriplett.org> Acked-by: Borislav Petkov <bp@suse.de> Cc: Rob Landley <rob@landley.net> Cc: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
74a475acea
commit
9547c706d2
@ -112,7 +112,15 @@ to do frotz", as if you are giving orders to the codebase to change
|
|||||||
its behaviour.
|
its behaviour.
|
||||||
|
|
||||||
If the patch fixes a logged bug entry, refer to that bug entry by
|
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 https://lkml.kernel.org/
|
||||||
|
redirector with a Message-Id, to ensure that the links cannot become
|
||||||
|
stale.
|
||||||
|
|
||||||
|
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
|
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
|
SHA-1 ID of the commit. Please also include the oneline summary of
|
||||||
|
Loading…
Reference in New Issue
Block a user