I am using Git version 1.9.1 on Ubuntu 14.04.
I have tested the core.autocrlf
behaviour in a fresh repo with a DOS-format and a Unix-format file and confirmed that git add
with autocrlf=true
does, as expected, produce a warning: LF will be replaced by CRLF in ...
message for the Unix-format file, and produces no messages for either file when autocrlf=false
. (I'm not clear in this case why it decided to use DOS line endings rather than Unix ones in the repo, but I'm not sure that's important here.)
However, in another repo, despite having autocrlf=true
, it keeps telling me that it's going to convert some files:
$ git config core.autocrlf
false
$ git add lib/node_modules/pulp/node_modules/webpack/node_modules/webpack-core/node_modules/source-list-map/test/fixtures/from-to-tests/null-source.input.map
warning: CRLF will be replaced by LF in lib/node_modules/pulp/node_modules/webpack/node_modules/webpack-core/node_modules/source-list-map/test/fixtures/from-to-tests/null-source.input.map.
The file will have its original line endings in your working directory.
$
I can't figure out why it's doing this. I'm looking for either an explanation of the problem or clues on how to debug it.
Additional notes:
- No, there isn't a
.gitattributes
file in the repo. But it raises an interesting point, should it make a difference ifautocrlf
is set to false? - And no, I just checked carefully and the file has a 0x0a after every 0x0d, and a 0x0d before every 0x0a.