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 <cody.taylor@maternityneighborhood.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Mar 13, 2015 at 00:02 UTC
b25c4699569f8cef23b21a8441bb90beb28ffa36
1 file changed
+5
Documentation/SubmittingPatches
+5
@@ -135,6 +135,11 @@ that is fine, but please mark it as such.
135
136
(4) Sending your patches.
137
138
+Learn to use format-patch and send-email if possible. These commands
139
+are optimized for the workflow of sending patches, avoiding many ways
140
+your existing e-mail client that is optimized for "multipart/*" mime
141
+type e-mails to corrupt and render your patches unusable.
142
+
143
People on the Git mailing list need to be able to read and
144
comment on the changes you are submitting. It is important for
145
a developer to be able to "quote" your changes, using standard