summaryrefslogtreecommitdiff
path: root/t/t5515/refs.br-remote-explicit-merge_remote-explicit
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2011-04-08 18:40:36 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2011-04-26 15:07:02 -0700
commit4d03c18a3ea18138c24d379ccc25e219a36ca1ef (patch)
tree67b3785d209821d96dfe4e796eb88a714007d90d /t/t5515/refs.br-remote-explicit-merge_remote-explicit
parentGit 1.7.4.5 (diff)
downloadtgif-4d03c18a3ea18138c24d379ccc25e219a36ca1ef.tar.xz
pretty: quote rfc822 specials in email addresses
If somebody has a name that includes an rfc822 special, we will output it literally in the "From:" header. This is usually OK, but certain characters (like ".") are supposed to be enclosed in double-quotes in a mail header. In practice, whether this matters may depend on your MUA. Some MUAs will happily take in: From: Foo B. Bar <author@example.com> without quotes, and properly quote the "." when they send the actual mail. Others may not, or may screw up harder things like: From: Foo "The Baz" Bar <author@example.com> For example, mutt will strip the quotes, thinking they are actual syntactic rfc822 quotes. So let's quote properly, and then (if necessary) we still apply rfc2047 encoding on top of that, which should make all MUAs happy. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/refs.br-remote-explicit-merge_remote-explicit')
0 files changed, 0 insertions, 0 deletions