{"thread":{"id":"38794","subject":"Re: [Documentation/RFC] Submitting Patches","startedAt":"2015-03-13T08:18:33Z","lastAt":"2015-03-13T08:18:33Z","messageCount":1,"participants":["Cody Taylor"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"257638","messageId":"CAHWMk2ZE1bY0ABcMRTqHGW3oY-oWXaaKdaBOzo2rVyZjJPRzQQ@mail.gmail.com","threadId":"38794","inReplyTo":null,"subject":"Re: [Documentation/RFC] Submitting Patches","fromName":"Cody Taylor","fromEmail":"cody.taylor@maternityneighborhood.com","sentAt":"2015-03-13T08:18:33Z","receivedAt":"2015-03-13T08:18:33Z","isPatch":false,"sender":{"key":"cody.taylor@maternityneighborhood.com","avatar":null},"body":"Junio C Hamano <gitster@pobox.com> wrote:\n> Subject: SubmittingPatches: nudge to use send-email\n>\n> In step \"(4) Sending your patches\", we instruct users to do an\n> inline patch, avoid breaking whitespaces, avoid attachments,\n> use [PATCH v2] for second round, etc., all of which send-email\n> knows how to do.\n\nThe idea that `git send-email` does all of the suggestions really should\nbe reflected in the documentation.\n\n> Mention send-email at least once to gently nudge the user to (learn\n> to) use it.\n\nIf the tool is good, do not tippy toe around the subject. Write plain text\ne-mail is a strange enough experience today, the documentation should\nplainly state that \"git send-email\" is likely the easiest solution to sending\na patch or series of patches.\n\nSuggesting: Cody A Taylor <cody.taylor@maternityneighborhood.com>\n---\n Documentation/SubmittingPatches | 8 ++++++++\n 1 file changed, 8 insertions(+)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex ef0eeb40cd22..702f1ace08ae 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -136,6 +136,14 @@ that is fine, but please mark it as such.\n\n (4) Sending your patches.\n\n+The \"git format-patch\" and \"git send-email\" commands are\n+complemtary to one another. They are optimized to make the work\n+flow of sending patches much easier. Primarily, using these\n+commands avoids the need to re-learn your existing e-mail client\n+that is optimized for \"multipart/*\" mime type e-mails. Using\n+these tools you will midigate the simple problems that cause poorly\n+formatted e-mails.\n+\n People on the Git mailing list need to be able to read and\n comment on the changes you are submitting.  It is important for\n a developer to be able to \"quote\" your changes, using standard\n--\nv2.3.2\n"}]}