summaryrefslogtreecommitdiff
path: root/line-range.c
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2017-05-09 14:54:32 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-05-10 13:32:51 +0900
commit2779f665054c3ba85c1ee298929e640149d84b1e (patch)
tree5e8621b324fbc1d4121de6a345158a570e4d9aa2 /line-range.c
parentFix the remaining tests that failed with core.autocrlf=true (diff)
downloadtgif-2779f665054c3ba85c1ee298929e640149d84b1e.tar.xz
t4051: mark supporting files as requiring LF-only line endings
The test t4051-diff-function-context.sh passes on Linux when core.autocrlf=true even without marking its support files as LF-only, but they fail when core.autocrlf=true in Git for Windows' SDK. The reason is that `grep ... >file.c.new` will keep CR/LF line endings on Linux (obviously treating CRs as if they were regular characters), but will be converted to LF-only line endings with MSYS2's grep that is used in Git for Windows. As we do not want to validate the way the available `grep` works, let's just mark the input as LF-only and move on. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Reviewed-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'line-range.c')
0 files changed, 0 insertions, 0 deletions