Hello, I'd like to report a bug. There's an incompatibility between the way TortoiseGit sends patches by e-mail and their handling by git-mailsplit. The mail sent by TortoiseGit specifies the Content-Type header as "Content-Type: text/plain; boundary=WC_MAIL_PaRt_BoUnDaRy_05151998". git-mailsplit then misinterprets it and treats it as empty patch. While TortoiseGit should not be sending the boundary parameter, it is perfectly valid e-mail according to RFC 5322 and MIME RFCs. The "boundary" parameter should be ignored for anything but "multipart" Content-Types. Best regards, Filip Navara P.S. I'm not subscribed to the mailing lists, so please CC me if you reply. -- 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