| commit | 385dbdb3d61d55bf4cbdf1e2926456da9e7b6e7f | |
| author | Carlos R. Mafra <crmafra@gmail.com> | |
| Sat, 14 Jan 2012 15:18:32 +0000 (14 15:18 +0000) | ||
| committer | Carlos R. Mafra <crmafra@gmail.com> | |
| Sat, 14 Jan 2012 15:34:44 +0000 (14 15:34 +0000) | ||
| tree | adff702ab60625881437a297703d3ee2e16b77b7 | treesnapshot (tar.gz zip) |
| parent | 8b049dec73973f39735d512c270837cab69541f3 | commitdiff |
Steal documentation with tips on email clients
Applying patches without needing to fix them first helps me save time,
and this file (stolen from the linux kernel documentation) contains some
valuable tips to configure email clients to not mangle the patches you send.
The goal is that patches are sent in the body of the email (to ease review)
and be applied directly with 'git am'.
I personally use mutt as mail client and xjed as an editor. I insert the patch
in the body of the email using xjed's "Insert file" menu operation. That
works fine, but this documentation file helps you with more choices.
Applying patches without needing to fix them first helps me save time,
and this file (stolen from the linux kernel documentation) contains some
valuable tips to configure email clients to not mangle the patches you send.
The goal is that patches are sent in the body of the email (to ease review)
and be applied directly with 'git am'.
I personally use mutt as mail client and xjed as an editor. I insert the patch
in the body of the email using xjed's "Insert file" menu operation. That
works fine, but this documentation file helps you with more choices.
| email-clients.txt | [new file with mode: 0644] | blob |