warning: CRLF will be replaced by LF code example

Example 1: The file will have its original line endings in your working directory

# If you are a single developer working on a windows machine,
# and you don't care that git automatically replaces LFs to CRLFs,
# you can turn this warning off by typing the following in the git command line

git config core.autocrlf true

Example 2: warning: LF will be replaced by CRLF

git config --global core.autocrlf true

Example 3: LF will be replaced by CRLF in assets

git config core.autocrlf true

Example 4: lf will be replaced by crlf in web/app.css.

#If you are a single developer working on a windows machine, and you don't care
#that git automatically replaces LFs to CRLFs, you can turn this warning off by
#typing the following in the git command line
git config core.autocrlf true

#If you’re programming on Windows and working with people who are not (or vice-versa), 
#you’ll probably run into line-ending issues at some point.
$ git config --global core.autocrlf true

#If you’re on a Linux or Mac system that uses LF line endings, then you don’t 
#want Git to automatically convert them when you check out files; however, if a 
#file with CRLF endings accidentally gets introduced, then you may want Git to 
#fix it.
$ git config --global core.autocrlf input

#If you’re a Windows programmer doing a Windows-only project, 
#then you can turn off this functionality, recording the carriage returns in 
#the repository by setting the config value to false:
$ git config --global core.autocrlf false

Example 5: warning: LF will be replaced by CRLF

git config core.autocrlf true

Example 6: warning: LF will be replaced by CRLF in

$ git config --global core.autocrlf input