summaryrefslogtreecommitdiff
path: root/Documentation/fetch-options.txt
diff options
context:
space:
mode:
authorLibravatar Brandon Casey <drafnel@gmail.com>2009-06-07 19:25:58 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2009-06-09 00:15:57 -0700
commita3a8262bf6e2acbb1b61cc25be073713e183c766 (patch)
treefc6a602e4c290b6c285da33a59abee5aa963b81e /Documentation/fetch-options.txt
parentsymlinks.c: small style cleanup (diff)
downloadtgif-a3a8262bf6e2acbb1b61cc25be073713e183c766.tar.xz
git-send-email.perl: improve detection of MIME encoded-words
According to rfc2047, an encoded word has the following form: encoded-word = "=?" charset "?" encoding "?" encoded-text "?=" charset = token encoding = token token = <Any CHAR except SPACE, CTLs, and especials> especials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / " <"> / "/" / "[" / "]" / "?" / "." / "=" encoded-text = <Any printable ASCII character other than "?" or SPACE> And rfc822 defines CHARs and CTLs as: CHAR = <any ASCII character> ; ( 0-177, 0.-127.) CTL = <any ASCII control ; ( 0- 37, 0.- 31.) character and DEL> ; ( 177, 127.) The original code only detected rfc2047 encoded strings when the charset was UTF-8. This patch generalizes the matching expression and breaks the check for an rfc2047 encoded string into its own function. There's no real functional change, since any properly rfc2047 encoded string would have fallen through the remaining 'if' statements and been returned unchanged. Signed-off-by: Brandon Casey <drafnel@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/fetch-options.txt')
0 files changed, 0 insertions, 0 deletions