On Friday 15 April 2011, Jonathan Nieder wrote: > I'm not sure what gotchas these hints are meant to work around. > They might be completely false. These suggestion are there to warn and help about space/word wrap mangling, and to send a patch in the mail body (as per SubmittingPatches). > A quick search for "how to send patches with KMail" gave me the > "external editor" trick. Do these instructions work? ;-) They do work, but maybe they are not so important, since they're helpful only for the one-time-hack-patch and I-don't-want-to-setup- git-send-email. When there are more than 3 or 4 patches to send, 'git send-email' (plus msmtp, if needed) is more comfortable. There is however, an helpful hint in http://wiki.winehq.org/GitWine (never tried it, and I'd tend to prefer 'git send-email' anyway, don't know if this should be mentioned in git docs): Using local KMail folders, you can use the following approach: git format-patch --stdout --keep-subject origin | formail -s procmail Assuming you don't already use procmail to sort your email, you can use the following .procmailrc :0 /home/username/.maildir/ Now, all you need to do is to set up a new receiving account in KMail that collects mail from /home/username/.maildir and filter emails coming in on that account to your drafts folder. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html