The file will have its original line endings in your working directory. However, doing just this tonight I ended up reverting to git mv. The file will have its original line endings in your working directory warning: LF will be replaced by CRLF in phpunit.xml. lf will be replaced warning: LF will be replaced by CRLF in bike_share.ipynb. git warning lf will be replaced by crlf Code Example CRLF: Carriage Return and Line Feed or CRLF is like combining the power of both it moves the cursor to the new line and the beginning of the same line. こちらの記事が参考になりました。. Git: warning: LF will be replaced by CRLF in # Re-add all the deleted files to the index # You should get lots of messages like: "warning: CRLF will be replaced by LF in ." warning: lf will be replaced by crlf git diff I solved it this way: git diff will give this warning: warning: LF will be replaced by CRLF in constants.py. warning: LF will be replaced by CRLF in .npmrc git diff lf will be … In windows a line is represented with a carriage return (CR) and a line feed (LF) thus (CRLF). The file will have its original line endings in your working directory. Git This setting forces Git to normalize line endings to LF on checkin and prevents conversion to CRLF when the file is checked out. Unix represents the end of a line as a line feed (LF) while windows uses carriage return and line feed (CRLF). I noticed that some files that hadn’t been touched were included in the commit. warning: LF will be replaced by CRLF in index.js. The file will have its original line endings in your working directory. warning: CRLF will be replaced by LF in .gitattributes. The file will have its original line endings in your working directory warning lf will be replaced by crlf meaning fatal: LF would be replaced by CRLF in .gitignore after running git add git warning: LF will be replaced by CRLF in windows git warning: LF will be replaced by CRLF in .htaccess.sample. git warning: LF will be replaced by CRLF in Code Example warning: lf will be replaced by crlf git diff