Geert Uytterhoeven dixit:
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.
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)?
Honestly, the requirement to mail patches inline and not MIME
encoded reminds me of my time trying to contribute to OpenBSD
(before that ended due to personal, not technical, issues),
where the lead developers used non-MIME mailx(1) to read mails…
I think accepting an encoded mail (not necessarily multipart,
i.e. “attachment”, but to put it through the SMTP path) and
decoding it in the “git am” part should be possible.
bye,
//mirabilos
--
13:37⎜«Natureshadow» Deep inside, I hate mirabilos. I mean, he's a good
guy. But he's always right! In every fsckin' situation, he's right. Even
with his deeply perverted taste in software and borked ambition towards
broken OSes - in the end, he's damn right about it :(! […] works in mksh
--
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
