path: root/Documentation
diff options
authorJunio C Hamano <>2015-03-13 07:02:15 (GMT)
committerJunio C Hamano <>2015-03-15 21:31:42 (GMT)
commitb25c4699569f8cef23b21a8441bb90beb28ffa36 (patch)
tree5cd2fc8d9e2700820279819ea3a55208ad8c70a7 /Documentation
parent282616c72d1d08a77ca4fe1186cb708c38408d87 (diff)
SubmittingPatches: encourage users to use format-patch and send-email
In step "(4) Sending your patches", we instruct users to do an inline patch, avoid breaking whitespaces, avoid attachments, use [PATCH v2] for second round, etc., all of which format-patch and send-email combo know how to do well. The need was identified by, and the text is based on the work by Cody Taylor. Suggested-by: Cody Taylor <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation')
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index e6d46ed..38e4ae2 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -135,6 +135,11 @@ that is fine, but please mark it as such.
(4) Sending your patches.
+Learn to use format-patch and send-email if possible. These commands
+are optimized for the workflow of sending patches, avoiding many ways
+your existing e-mail client that is optimized for "multipart/*" mime
+type e-mails to corrupt and render your patches unusable.
People on the Git mailing list need to be able to read and
comment on the changes you are submitting. It is important for
a developer to be able to "quote" your changes, using standard