diff options
author | brian m. carlson <sandals@crustytoothpaste.net> | 2019-04-13 22:45:51 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2019-04-14 11:47:03 +0900 |
commit | 74d76a17013411d72ebda7c230b9898f3adb1fcc (patch) | |
tree | f4d337dc9f436de9fb381f002c103181e65fd65a /Documentation/SubmittingPatches | |
parent | mingw: allow building with an MSYS2 runtime v3.x (diff) | |
download | tgif-74d76a17013411d72ebda7c230b9898f3adb1fcc.tar.xz |
send-email: default to quoted-printable when CR is present
In 7a36987fff ("send-email: add an auto option for transfer encoding",
2018-07-08), git send-email learned how to automatically determine the
transfer encoding for a patch. However, the only criterion considered
was the length of the lines.
Another case we need to consider is that of carriage returns. Because
emails have CRLF endings when canonicalized, we don't want to write raw
carriage returns into a patch, lest they be stripped off as an artifact
of the transport. Ensure that we choose quoted-printable encoding if the
patch we're sending contains carriage returns.
Note that we are guaranteed to always correctly encode carriage returns
when writing quoted-printable since we explicitly specify the line
ending as "\n", forcing MIME::QuotedPrint to encode our carriage return
as "=0D".
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/SubmittingPatches')
0 files changed, 0 insertions, 0 deletions