On Tue, Jun 5, 2012 at 7:57 PM, Thorsten Glaser <tg@xxxxxxxxx> wrote:
Andreas Schwab dixit:
That is not true. 8BITMIME will handle that correctly.
8BITMIME is not ubiquitous. Worse, most current MTAs do *not* handle
conversion of an 8bit mail to QP/Base64 correctly and violate the RFC.
I added a Russian word in Cyrilic (UTF8) to a file in a Linux kernel
git repository.
I commited it with a commit message containing Cyrillic, too.
I used "git format-patch" to create a patch, which contains a.o. the following
headers:
| Content-Type: text/plain; charset=UTF-8
| Content-Transfer-Encoding: 8bit
I used "git send-email" to send it to me (it goes out via my provider, passes
by linux-m68k.org/nerdnet.nl, and arrives at gmail).
The patch looks fine in the gmail web interface.
I used "Show original" to open the original email incl. headers. It still has
| Content-Type: text/plain; charset=UTF-8
| Content-Transfer-Encoding: 8bit
No Base64 or QP involved.
I saved it to a file and removed the first line.
I could apply the patch fine using "git am".
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
