| commit | a61c0ffa4474ad6dcec18a5454630371106710f4 | |
| author | Jay Soffian <jaysoffian@gmail.com> | |
| Tue, 31 Mar 2009 16:22:14 +0000 (31 12:22 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 2 Apr 2009 17:46:21 +0000 (2 10:46 -0700) | ||
| tree | 13050336905d92f95adaaff77bc7629c8d053d7a | treesnapshot (tar.gz zip) |
| parent | 3b3637c3f1d752e6e6d559f30cc53bbec18537ef | commitdiff |
send-email: ensure quoted addresses are rfc2047 encoded
sanitize_address assumes that quoted addresses (e.g., "first last"
<first.last@example.com) do not need rfc2047 encoding, but this is
not always the case.
For example, various places in send-email extract addresses using
parse_address_line. parse_address_line returns the addresses already
quoted (e.g., "first last" <first.last@example.com), but not rfc2047
encoded.
This patch makes sanitize_address stricter about what needs rfc2047
encoding and adds a test demonstrating where I noticed the problem.
Signed-off-by: Jay Soffian <jaysoffian@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
sanitize_address assumes that quoted addresses (e.g., "first last"
<first.last@example.com) do not need rfc2047 encoding, but this is
not always the case.
For example, various places in send-email extract addresses using
parse_address_line. parse_address_line returns the addresses already
quoted (e.g., "first last" <first.last@example.com), but not rfc2047
encoded.
This patch makes sanitize_address stricter about what needs rfc2047
encoding and adds a test demonstrating where I noticed the problem.
Signed-off-by: Jay Soffian <jaysoffian@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| git-send-email.perl | diffblobblamehistory | |
| t/t9001-send-email.sh | diffblobblamehistory |