diff options
author | Ray Satiro <raysatiro@yahoo.com> | 2014-09-12 10:22:34 +0200 |
---|---|---|
committer | Daniel Stenberg <daniel@haxx.se> | 2014-09-12 10:22:34 +0200 |
commit | 006b61eb0b262619c750a81e5b0c1f8909cdfc80 (patch) | |
tree | 75ba6788219c524dc7dc012dc21de8987c0a0e3e /perl | |
parent | 82b8b6865c5c65ddc2c33c32f13047be47c16944 (diff) |
newlines: fix mixed newlines to LF-only
I use the curl repo mainly on Windows with the typical Windows git
checkout which converts the LF line endings in the curl repo to CRLF
automatically on checkout. The automatic conversion is not done on files
in the repo with mixed line endings. I recently noticed some weird
output with projects/build-openssl.bat that I traced back to mixed line
endings, so I scanned the repo and there are files (excluding the
test data) that have mixed line endings.
I used this command below to do the scan. Unfortunately it's not as easy
as git grep, at least not on Windows. This gets the names of all the
files in the repo's HEAD, gets each of those files raw from HEAD, checks
for mixed line endings of both LF and CRLF, and prints the name if
mixed. I excluded path tests/data/test* because those can have mixed
line endings if I understand correctly.
for f in `git ls-tree --name-only --full-tree -r HEAD`;
do if [ -n "${f##tests/data/test*}" ];
then git show "HEAD:$f" | \
perl -0777 -ne 'exit 1 if /([^\r]\n.*\r\n)|(\r\n.*[^\r]\n)/';
if [ $? -ne 0 ];
then echo "$f";
fi;
fi;
done
Diffstat (limited to 'perl')
0 files changed, 0 insertions, 0 deletions