Bug#605767: git-email: UTF-8 content in To: causes Subject: to also be RFC2047 encoded

2010-12-03 Thread Sascha Silbe
Package: git-email Version: 1:1.7.2.3-2 Severity: minor If To: contains a non-ASCII character, the Subject: header is RFC2047 encoded even if it contains only ASCII characters: === Begin === From: Sascha Silbe sascha-...@silbe.org To: =?UTF-8?q?St=C3=A9phane=20Magnenat?=

Bug#605767: git-email: UTF-8 content in To: causes Subject: to also be RFC2047 encoded

2010-12-03 Thread Jonathan Nieder
Hi Sascha, Sascha Silbe wrote: If To: contains a non-ASCII character, the Subject: header is RFC2047 encoded even if it contains only ASCII characters: === Begin === From: Sascha Silbe sascha-...@silbe.org To: =?UTF-8?q?St=C3=A9phane=20Magnenat?= stephane.magne...@mavt.ethz.ch Subject:

Bug#605767: git-email: UTF-8 content in To: causes Subject: to also be RFC2047 encoded (Bug#605767)

2010-12-03 Thread Sascha Silbe
Excerpts from Jonathan Nieder's message of Fri Dec 03 11:20:37 +0100 2010: The subject seems to be ASCII. Ideas? Hmm, maybe the fact that it asked for the encoding (because the cover letter contained the recipients real name in the body) played a role. Shame on me for not posting the entire