aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/SubmittingPatches
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/SubmittingPatches')
-rw-r--r--Documentation/SubmittingPatches15
1 files changed, 14 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 4710e4afef19..d603fa078235 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -718,8 +718,21 @@ generates appropriate diffstats by default.)
718See more details on the proper patch format in the following 718See more details on the proper patch format in the following
719references. 719references.
720 720
72115) Explicit In-Reply-To headers
722--------------------------------
723
724It can be helpful to manually add In-Reply-To: headers to a patch
725(e.g., when using "git send email") to associate the patch with
726previous relevant discussion, e.g. to link a bug fix to the email with
727the bug report. However, for a multi-patch series, it is generally
728best to avoid using In-Reply-To: to link to older versions of the
729series. This way multiple versions of the patch don't become an
730unmanageable forest of references in email clients. If a link is
731helpful, you can use the https://lkml.kernel.org/ redirector (e.g., in
732the cover email text) to link to an earlier version of the patch series.
733
721 734
72215) Sending "git pull" requests 73516) Sending "git pull" requests
723------------------------------- 736-------------------------------
724 737
725If you have a series of patches, it may be most convenient to have the 738If you have a series of patches, it may be most convenient to have the