From: Thorsten Glaser <tg@mirbsd.org>
To: linux-m68k@vger.kernel.org
Subject: Re: [PATCH] [m68k] Atari: support for NetUSBee register access to isp116x.h
Date: Tue, 5 Jun 2012 15:51:39 +0000 (UTC) [thread overview]
Message-ID: <loom.20120605T174709-209@post.gmane.org> (raw)
In-Reply-To: CAOmrzk+2bYgDNtcW6DVy4WYT2i+07n8xR4bbNbwFJ@mail.gmail.com
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@mydomain.com <"$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
next prev parent reply other threads:[~2012-06-05 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 22:48 [PATCH] [m68k] Atari: support for NetUSBee register access to isp116x.h Michael Schmitz
2012-05-29 20:46 ` Geert Uytterhoeven
2012-06-01 18:46 ` Michael Schmitz
2012-06-01 19:06 ` Geert Uytterhoeven
[not found] ` <CAOmrzk+2bYgDNtcW6DVy4WYT2i+07n8xR4bbNbwFJ@mail.gmail.com>
2012-06-05 15:51 ` Thorsten Glaser [this message]
2012-06-05 16:20 ` Geert Uytterhoeven
2012-06-05 16:26 ` Thorsten Glaser
2012-06-05 16:45 ` Geert Uytterhoeven
2012-06-05 17:53 ` Andreas Schwab
2012-06-05 17:57 ` Thorsten Glaser
2012-06-05 18:36 ` Andreas Schwab
2012-06-05 19:52 ` Geert Uytterhoeven
2012-06-05 19:59 ` Thorsten Glaser
2012-06-05 16:38 ` Andreas Schwab
2012-06-05 16:51 ` Thorsten Glaser
2012-06-05 19:43 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20120605T174709-209@post.gmane.org \
--to=tg@mirbsd.org \
--cc=linux-m68k@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox