aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/SubmittingPatches
diff options
context:
space:
mode:
authorJakub Wilk <jwilk@jwilk.net>2015-12-15 11:00:27 (GMT)
committerJonathan Corbet <corbet@lwn.net>2016-01-25 19:30:18 (GMT)
commit6ac9937c976443743962cfe7b6893163adadbda5 (patch)
tree89cfa61b58d28ab09290ce00bb435b75565b77b5 /Documentation/SubmittingPatches
parent92e963f50fc74041b5e9e744c330dca48e04f08d (diff)
downloadkernel_replicant_linux-6ac9937c976443743962cfe7b6893163adadbda5.zip
kernel_replicant_linux-6ac9937c976443743962cfe7b6893163adadbda5.tar.gz
kernel_replicant_linux-6ac9937c976443743962cfe7b6893163adadbda5.tar.bz2
SubmittingPatches: fix spelling of "git send-email"
Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/SubmittingPatches')
-rw-r--r--Documentation/SubmittingPatches2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index d603fa0..8c79f1d 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -722,7 +722,7 @@ references.
--------------------------------
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
+(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