0b689562ca
When SMTP servers receive 8-bit email messages, possibly with only LF as line ending, some of them decide to change said LF to CRLF. Some mailing list softwares, when receive 8-bit email messages, decide to encode those messages in base64 or quoted-printable. If an email is transfered through above mail servers, then distributed by such mailing list softwares, the recipients will receive an email contains a patch mungled with CRLF encoded inside another encoding. Thus, such CR (in CRLF) couldn't be dropped by "mailsplit". Hence, the mailed patch couldn't be applied cleanly. Such accidents have been observed in the wild [1]. Instead of silently rejecting those messages, let's give our users some warnings if such CR (as part of CRLF) is found. [1]: https://nmbug.notmuchmail.org/nmweb/show/m2lf9ejegj.fsf%40guru.guru-group.fi Signed-off-by: Đoàn Trần Công Danh <congdanhqx@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
23 lines
734 B
Plaintext
23 lines
734 B
Plaintext
---%%
|
|
configure | 2 +-%%
|
|
1 file changed, 1 insertion(+), 1 deletion(-)%%
|
|
%%
|
|
diff --git a/configure b/configure%%
|
|
index db3538b3..f7c1c095 100755%%
|
|
--- a/configure%%
|
|
+++ b/configure%%
|
|
@@ -814,7 +814,7 @@ if [ $have_python3 -eq 1 ]; then%%
|
|
printf "%%Checking for python3 pytest (>= 3.0)... "%%
|
|
conf=$(mktemp)%%
|
|
printf "[pytest]\nminversion=3.0\n" > $conf%%
|
|
- if pytest-3 -c $conf --version >/dev/null 2>&1; then%%
|
|
+ if "$python" -m pytest -c $conf --version >/dev/null 2>&1; then%%
|
|
printf "Yes.\n"%%
|
|
have_python3_pytest=1%%
|
|
else%%
|
|
-- %%
|
|
2.28.0%%
|
|
_______________________________________________
|
|
example mailing list -- list@example.org
|
|
To unsubscribe send an email to list-leave@example.org
|