Git uses an error under Windows:
Warning:lf'll be replaced by CRLF inxxxx.xx (filename) The file would have the IT original line ending in your working directory. Turn In the xxx.xx file, LF will be replaced by CRLF. In the workspace (working directory), this file will maintain its original line break. (Line ending: End, newline)
Annotations:
Lf:line Feed Line
Crlf:carriage return line Feed enter newline key
1, different operating systems, processing end-of-line terminator method is different :
Under Windows: CRLF (indicates the end of a sentence using carriage return two characters, i.e. "\ r \ n" line wrapping under Windows)
Under Unix: LF (denotes end of sentence, use only line wrapping )
Under Mac: CR (means only carriage return is used)
2, git processing "line ending"
Core.autocrlf is a variable in git that handles line ending, and you can set 3 values: True,false,inout.
(1) Set to True "config--global core.autocrlf true"
When set to true, this means that when you add a file to a git repository at any time, git will treat it as a text file.
It will turn the CRLF into LF.
(2) set to False "config--global Core.autocrlf false"
When set to False, line endings will not do the conversion operation. The text file stays the way it was .
(3) When you set the file to input git repository, git put CRLF programming lf. When someone check the code or the LF mode. Therefore , do not use this setting under the Windows operating system .
In summary, the reason for the above warning is:
The newline character in Windows is CRLF, and the newline character under Linux is LF (using git command-line git Bash, which is actually equivalent to the Linux environment ), so when performing the git add xxx.xx operation, This error message will appear!
Workaround:
<1> delete. Git "rm-rf. Git"
<2> Disable auto-conversion, setting:git config--global core.autocrlf false
Re-initialize and perform the add operation:
<3> "git init"
<4> "git add xxx.xx"
Windows git uses error: Warning:lf'll be replaced by CRLF inxxxx.xx