> * tb/check-crlf-for-safe-crlf (2017-11-27) 1 commit > (merged to 'next' on 2017-12-05 at 7adaa1fe01) > + convert: tighten the safe autocrlf handling > > The "safe crlf" check incorrectly triggered for contents that does > not use CRLF as line endings, which has been corrected. > > Broken on Windows??? > cf. <da960dce-0635-47cf-b3c4-813302179...@gmail.com>
Yes, broken on Windows. A fix is coming the next days.