path: root/Documentation/SubmittingPatches
diff options
authorChris Metcalf <cmetcalf@ezchip.com>2015-11-05 20:21:47 (GMT)
committerJonathan Corbet <corbet@lwn.net>2015-11-11 17:06:00 (GMT)
commitd7ac8d85d39f460df9204b875eb985e18a5c523b (patch)
treefc010fa0764b883d6dbeac2f272b7205d18cddfe /Documentation/SubmittingPatches
parenta907c907656bdbe082555a579ee6058a873b6e3a (diff)
Documentation/SubmittingPatches: discuss In-Reply-To
Add a paragraph suggesting best practices for when to link patches to previous LKML messages via In-Reply-To. Signed-off-by: Chris Metcalf <cmetcalf@ezchip.com> [jc: moved the added text to a separate section] Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/SubmittingPatches')
1 files changed, 14 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index fd89b04..0db4e10 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -718,8 +718,21 @@ generates appropriate diffstats by default.)
See more details on the proper patch format in the following
+15) Explicit In-Reply-To headers
+It can be helpful to manually add In-Reply-To: headers to a patch
+(e.g., when using "git send email") to associate the patch with
+previous relevant discussion, e.g. to link a bug fix to the email with
+the bug report. However, for a multi-patch series, it is generally
+best to avoid using In-Reply-To: to link to older versions of the
+series. This way multiple versions of the patch don't become an
+unmanageable forest of references in email clients. If a link is
+helpful, you can use the https://lkml.kernel.org/ redirector (e.g., in
+the cover email text) to link to an earlier version of the patch series.
-15) Sending "git pull" requests
+16) Sending "git pull" requests
If you have a series of patches, it may be most convenient to have the