Paul Eggert <eggert@cs.ucla.edu> writes:
$ git format-patch 5be5ee3dd453c5b575f6336eada9390fb205717a^! 0001-Mention-more-JavaScript-libraries.patch $ git format-patch c25e1180cf3ec34d6c731d5ec16739d6d2ca8fc2^! 0001-More-spelling-and-accent-fixes.patch $ grep UTF-8 0* 0001-Mention-more-JavaScript-libraries.patch: <meta http-equiv="Content-type" content='text/html; charset="UTF-8"'>
The first patch is labeled as UTF-8
No, it isn't.
It seems crazy to me that I would need to specify an obscure option to have 'git format-patch' do the right thing. I run either git 1.9.3 (Fedora 20) or git 1.9.1 (Ubuntu 14.04) and neither version documents sendmail.assume8bitEncoding or --8bit-encoding in its man pages.
See git-send-email(1). Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."