On Tue, Jun 5, 2012 at 5:51 PM, Thorsten Glaser <[email protected]> wrote:
> ② $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 [email protected] <"$a"; done
"git send-email --to user@domain 00*"?
That can also take care of the threading.
> !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.
Does git send-email handle that correctly?
It will not use base64, as that's rejected by vger.kernel.org.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
