path: root/Documentation
diff options
authorJunio C Hamano <>2015-03-28 16:33:10 (GMT)
committerJunio C Hamano <>2015-03-28 16:33:10 (GMT)
commita5d31548544a709b18926220867fe1c1995fa9c3 (patch)
treef89cff3526de4cd12096bdd0be252bdfee1bbf18 /Documentation
parent73d8bfde32acae522b305f7742350d392e3f4e86 (diff)
parentb25c4699569f8cef23b21a8441bb90beb28ffa36 (diff)
Merge branch 'jc/submitting-patches-mention-send-email' into maint
Recommend format-patch and send-email for those who want to submit patches to this project. * jc/submitting-patches-mention-send-email: SubmittingPatches: encourage users to use format-patch and send-email
Diffstat (limited to 'Documentation')
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index ef0eeb4..98fc4cc 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -136,6 +136,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