Michael Schmitz <schmitzmic <at> googlemail.com> writes:
Which ones were affected? (Some were piped straight to sendmail while others used an e-mail client so I'd like to know what does actually work)
I found out that the following works reliably: ① scp/rsync files to a box I can mail from ② $EDITOR 00* ③ Add a To: line, and possibly a In-Reply-To: line referencing the Message-ID from the introductory mail (to get them threaded), to each file; save and exit https://www.mirbsd.org/jupp.htm ^Wthe editor ④ for a in 00*; do sendmail -oem -oi -t -f sender@xxxxxxxxxxxx <"$a"; done !BUT! This does only work if the patchfile does NOT contain any non-7bit characters. (This has affected me in the past when writing commit messages with “typogra’phic” marks, as I’m used to, nowadays.) There is *no* reliable way to transport inline patches through SMTP when either the commit message or the patches/the patch context contain such characters, as the SMTP transport path is probably not 8-bit transparent (may convert to QP or Base64, or strip bit7). So, in case I ever need to send such mails because the nōn-7bit part is in the patch (as opposed to the commit message), please bear with me when I need to attach them to a regular eMail. bye, //mirabilos – via GMane -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
