On Tue, Jun 5, 2012 at 6:26 PM, Thorsten Glaser <tg@xxxxxxxxx> wrote:
On Tue, Jun 5, 2012 at 5:51 PM, Thorsten Glaser <tg@xxxxxxxxxx> 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 sender@xxxxxxxxxxxx <"$a"; done
"git send-email --to user@domain 00*"?
You conveniently cut off Item #1 above, which involves copying
the patches to a machine that can mail out.
Rsync over ssh is the easy part ;-)
Alternatively, you probably can configure git to use ssh to call into sendmail
on a remote machine for the actual sending.
Does git send-email handle that correctly?
There is no way to handle 8bit correctly in SMTP, that does not
involve converting them to QP or Base64.
It will not use base64, as that's rejected by vger.kernel.org.
Interesting. How are QP encoded patches handled (other than,
what I assume, spit from Linux developers)?
Decent mail clients allow to save the mail body to a file, after
QP decoding?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
