CRLF line endings reported by jenkins workflow

[prjemian]

Is this a problem we should resolve?

+ git add .
warning: CRLF will be replaced by LF in _downloads/0a877a94f6f32b982b9a0c74073f6f01/write_nexus_file2.py.
The file will have its original line endings in your working directory
warning: CRLF will be replaced by LF in _downloads/464bd71626b8a660aadb9fc6cb05ae82/FDL.
The file will have its original line endings in your working directory
warning: CRLF will be replaced by LF in _downloads/dfc22f4a37f3414e5e8cc7135510b802/write_nexus_file.py.
The file will have its original line endings in your working directory
warning: CRLF will be replaced by LF in examples/epics/tree_structure.txt.
The file will have its original line endings in your working directory
warning: CRLF will be replaced by LF in examples/epics/write_nexus_file.py.
The file will have its original line endings in your working directory
warning: CRLF will be replaced by LF in examples/epics/write_nexus_file2.py.
The file will have its original line endings in your working directory
warning: CRLF will be replaced by LF in examples/napi-java-jnexus.bat.
The file will have its original line endings in your working directory

[prjemian]

Also related to #964

[PeterC-DLS]

Using

find . -not -type d -exec file "{}" \; | grep CRLF

in repo gives

./manual/source/FDL: ASCII text, with CRLF line terminators
./manual/source/examples/epics/write_nexus_file2.py: ASCII text, with CRLF line terminators
./manual/source/examples/epics/write_nexus_file.py: Python script, ASCII text executable, with CRLF line terminators
./manual/source/examples/epics/tree_structure.txt: ASCII text, with CRLF line terminators
./manual/source/examples/napi-java-jnexus.bat: ASCII text, with CRLF line terminators

I will convert those apart from the .bat file.