Mailing-patches - Revision history

Sjhill: /* Git */

2012-09-06T18:05:10Z

‎Git

2012-01-20T01:02:25Z

2011-12-09T10:29:09Z

‎See also: Use protocol independent URL.

2009-10-15T14:35:17Z

2007-06-06T09:43:40Z

2007-06-05T10:20:59Z

‎Thunderbird receipe #1

2007-06-05T10:20:43Z

‎Thunderbird receipe #2

2007-06-05T10:17:50Z

‎Thunderbird receipe #1

2007-06-05T10:16:12Z

‎Modern Thunderbird

2007-06-05T10:13:59Z

‎The MIME problem

@@ Line 28: / Line 28: @@
 == Git ==
-So you're developed your patches in git, have commited them to your git repository.  Then one of the easiest ways to send out is using <tt>git format-patch</tt> and <tt>git send-email</tt>.  It's going to format your emails the way recommended for submission in Documentation/ and make your life a lot easier.
+So you've developed your patches in git and commited them to your git repository. One of the easiest ways to send it out is using <tt>git format-patch</tt> and <tt>git send-email</tt>. It's going to format your emails the way recommended for submission in Documentation/ and make your life a lot easier.
 == Evolution ==

← Older revision		Revision as of 01:02, 20 January 2012
Line 26:		Line 26:

	which has led to the problem that a very significant fraction of patches had to be rejected simply because they didn't survive email transport. This page is trying to help you to fulfill the apparent contradiction. Keep in mind that the author of this page is a mutt user and would only touch a GUI mail client with a blowtorch.		which has led to the problem that a very significant fraction of patches had to be rejected simply because they didn't survive email transport. This page is trying to help you to fulfill the apparent contradiction. Keep in mind that the author of this page is a mutt user and would only touch a GUI mail client with a blowtorch.
		+
		+	== Git ==
		+	So you're developed your patches in git, have commited them to your git repository. Then one of the easiest ways to send out is using <tt>git format-patch</tt> and <tt>git send-email</tt>. It's going to format your emails the way recommended for submission in Documentation/ and make your life a lot easier.

	== Evolution ==		== Evolution ==

@@ Line 58: / Line 58: @@
 == See also ==
 * http://mbligh.org/linuxdocs/Email/Clients/Thunderbird Martin Bligh's page about survival with Thunderbird
-* http://lkml.org/lkml/2005/12/27/191 Discussion on linux-kernel on patch submission with Thunderbird.
+* [//lkml.org/lkml/2005/12/27/191 Discussion on linux-kernel] on patch submission with Thunderbird.
 * [[Wikipedia:MIME|MIME]]

@@ Line 6: / Line 6: @@
 * Do not address the receiver, no mail signatures, no PGP signatures.  If you follow these rules your email's body can be used without further editing as the log message greatly speeding up patch handling.
 * Don't forget to add a Signed-off-by: Your Name <your@email.address> line
 == The MIME problem ==

@@ Line 51: / Line 51: @@
 Others have suggested using an external editor which will show up in the compose editor and allow to include the patch file inline. For example see http://mozex.mozdev.org
 == See also ==
 * http://mbligh.org/linuxdocs/Email/Clients/Thunderbird Martin Bligh's page about survival with Thunderbird
 * http://lkml.org/lkml/2005/12/27/191 Discussion on linux-kernel on patch submission with Thunderbird.

@@ Line 35: / Line 35: @@
 * Use the Insert->Text_File pulldown menu to insert the patch from a file.  Do ''NOT'' use cut-and-paste to copy the patch, it'll likely corrupt the patch.
-== Thunderbird receipe #1 ==
+== Thunderbird recipe #1 ==
 Yep, the odd part is not to disable html email.  Then when composing a message, there is a drop-down box for a format selection.  While the cursor is in the body area, change the format from default "Body text" to ''Preformat'', and then copy-n-paste the patch.

@@ Line 36: / Line 36: @@
 == Thunderbird receipe #1 ==
-Yep, the odd part is not to disable html email.  Then when composing a message, there is a drop-down box for a format selection.  While the cursor is in the body area, change the format from default "Body text" to reformat, and then copy-n-paste the patch.
+Yep, the odd part is not to disable html email.  Then when composing a message, there is a drop-down box for a format selection.  While the cursor is in the body area, change the format from default "Body text" to ''Preformat'', and then copy-n-paste the patch.
 * Before starting to write the email, do Edit->Preferences, Composition tab, change "Wrap plain text messages at __ characters" to 0

@@ Line 31: / Line 31: @@
 == Modern Thunderbird ==
-* Set the formatting mode button just above the composition plane to ''Preformat''
+* Set the formatting mode button just above the composition pane to ''Preformat''
 * Write your log message.
-* Use the insert->Text_File pulldown menu to insert the patch from a file.  Do ''NOT'' use cut-and-paste to copy the patch, it'll lilely corrupt the patch.
+* Use the Insert->Text_File pulldown menu to insert the patch from a file.  Do ''NOT'' use cut-and-paste to copy the patch, it'll likely corrupt the patch.
 == Thunderbird receipe #1 ==

@@ Line 18: / Line 18: @@
 </pre>
-But due to ''brokenness'' of the most commonly used mail clients became necessary which generally scramble patches by:
+But due to ''brokenness'', the most commonly used mail clients generally scramble patches by:
 * chopping of trailing whitespace
 * converting tab characters to whitespace
-* break long lines into multiple lines.
+* breaking long lines into multiple lines.
-that has led to the problem that a very significant fraction of patches had to be rejected simply because they didn't survive email transport.  This page is trying to help you to fullfill the apparent contradiction.  Keep in mind that the author of this page is a mutt user and would only touch a GUI mail client with a blowtorch.
+which has led to the problem that a very significant fraction of patches had to be rejected simply because they didn't survive email transport.  This page is trying to help you to fulfill the apparent contradiction.  Keep in mind that the author of this page is a mutt user and would only touch a GUI mail client with a blowtorch.
 == Evolution ==