I would recommend, as I did in this SO question, to set it to false.
If you can avoid modifying any eol (with your editor), then it would be best to push back your work with those eol unchanged (i.e. “as you found them”).
More Related Contents:
- Trying to fix line-endings with git filter-branch, but having no luck
- Is it possible for git-merge to ignore line-ending differences?
- git diff – show me line ending changes?
- How to normalize working tree line endings in Git?
- What are these ^M’s that keep showing up in my files in emacs?
- Git push error ‘[remote rejected] master -> master (branch is currently checked out)’
- Git workflow and rebase vs merge questions
- What is the difference between origin and upstream on GitHub?
- Deleting a badly named git branch
- What does the term “porcelain” mean in Git?
- What does the git index contain EXACTLY?
- Git SSH authentication
- .gitignore and “The following untracked working tree files would be overwritten by checkout”
- How to git-cherry-pick only changes to certain files?
- How can sbt pull dependency artifacts from git?
- Git error when trying to push — pre-receive hook declined
- Untrack files from git temporarily
- Why git keeps showing my changes when I switch branches (modified,added, deleted files) no matter if I run git add or not?
- Does running git init twice initialize a repository or reinitialize an existing repo?
- git: undo all working dir changes including new files
- Checkout multiple git repos into same Jenkins workspace
- Moving a git repository up one hierarchy level
- How to apply a git patch from one repository to another?
- What does the caret (^) character mean in Git?
- Why git can’t do hard/soft resets by path?
- Is there a way to squash a number of commits non-interactively?
- How to colorify git errors, warnings and fatal messages?
- Git remove root commit
- Git rebase –preserve-merges fails
- Cygwin/Git error cygheap base mismatch detected