diff options
Diffstat (limited to 'Documentation/SubmittingPatches')
-rw-r--r-- | Documentation/SubmittingPatches | 15 |
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.) | |||
718 | See more details on the proper patch format in the following | 718 | See more details on the proper patch format in the following |
719 | references. | 719 | references. |
720 | 720 | ||
721 | 15) Explicit In-Reply-To headers | ||
722 | -------------------------------- | ||
723 | |||
724 | It 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 | ||
726 | previous relevant discussion, e.g. to link a bug fix to the email with | ||
727 | the bug report. However, for a multi-patch series, it is generally | ||
728 | best to avoid using In-Reply-To: to link to older versions of the | ||
729 | series. This way multiple versions of the patch don't become an | ||
730 | unmanageable forest of references in email clients. If a link is | ||
731 | helpful, you can use the https://lkml.kernel.org/ redirector (e.g., in | ||
732 | the cover email text) to link to an earlier version of the patch series. | ||
733 | |||
721 | 734 | ||
722 | 15) Sending "git pull" requests | 735 | 16) Sending "git pull" requests |
723 | ------------------------------- | 736 | ------------------------------- |
724 | 737 | ||
725 | If you have a series of patches, it may be most convenient to have the | 738 | If you have a series of patches, it may be most convenient to have the |