This question already has answers here: Git replacing LF with CRLF (24 answers) Closed 2 years ago.
git init
git add .
Gives the following warnings for many files:
The file will have its original line endings in your working directory. warning: LF will be replaced by CRLF in
What's the difference between LF and CRLF? What should I do about the warnings?
fatal: LF would be replaced by CRLF in Gemfile.lock, and git doesn't allow you to add a file. It is produced if you have safecrlf = true option set in any (global or local) .gitconfig file. Just hide it under comment if any.
$ dos2unix file will fix this for you
In Unix systems the end of a line is represented with a line feed (LF). In windows a line is represented with a carriage return (CR) and a line feed (LF) thus (CRLF). when you get code from git that was uploaded from a unix system they will only have an LF.
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 want to make an intelligent decision how git should handle this, read the documentation
Here is a snippet
Formatting and Whitespace Formatting and whitespace issues are some of the more frustrating and subtle problems that many developers encounter when collaborating, especially cross-platform. It’s very easy for patches or other collaborated work to introduce subtle whitespace changes because editors silently introduce them, and if your files ever touch a Windows system, their line endings might be replaced. Git has a few configuration options to help with these issues. core.autocrlf 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. This is because Windows uses both a carriage-return character and a linefeed character for newlines in its files, whereas Mac and Linux systems use only the linefeed character. This is a subtle but incredibly annoying fact of cross-platform work; many editors on Windows silently replace existing LF-style line endings with CRLF, or insert both line-ending characters when the user hits the enter key. Git can handle this by auto-converting CRLF line endings into LF when you add a file to the index, and vice versa when it checks out code onto your filesystem. You can turn on this functionality with the core.autocrlf setting. If you’re on a Windows machine, set it to true – this converts LF endings into CRLF when you check out code: $ 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. You can tell Git to convert CRLF to LF on commit but not the other way around by setting core.autocrlf to input: $ git config --global core.autocrlf input This setup should leave you with CRLF endings in Windows checkouts, but LF endings on Mac and Linux systems and in the repository. 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
If you want, you can deactivate this feature in your git core config using
git config core.autocrlf false
But it would be better to just get rid of the warnings using
git config core.autocrlf true
core.autocrlf false to begin with.
git config core.autocrlf is already set to true from the beginning, but the warnings still show up.
core.autocrlf from the .git/config file solved the problem for me.
Follow WeChat
Success story sharing
Want to stay one step ahead of the latest teleworks?
Subscribe Now相似问题
- What is the difference between 'git pull' and 'git fetch'?
- Difference between "git add -A" and "git add ."
- How do I make Git forget about a file that was tracked, but is now in .gitignore?
- How do I delete a Git branch locally and remotely?
- Undo a Git merge that hasn't been pushed yet
- How do I push a new local branch to a remote Git repository and track it too?
- How to determine the URL that a local Git repository was originally cloned from
- Throw away local commits in Git
- What does cherry-picking a commit with Git mean?
- Warning: push.default is unset; its implicit value is changing in Git 2.0
git config --global core.safecrlf falseto disable warning and keep it functioning. I got this command from here.core.autocrlf truedoes not turn off the warning for me, butcore.safecrlf falseas mentioned by Joel do.git config --global core.safecrlf falsesuppressed my annoying warningscore.safecrlftofalseyou are not "suppressing warnings." You are changing the behavior of howgitchecks in and checks out files, and it is that behavior that may or may not generate a warning. For me, I want it to betruebecause I am developing on Windows. However, I also wish to suppress the warnings, which is a hope that has no answer in this thread.