7

I am new to git, i was using svn earlier and we had issues caused by line-endings (CRLF and LF). now i am afraid this ll happen again in git too, the reason for my worry is different developers using different OS. and i am using a windows system with a Linux VM as my development environment. so project code is on linux and i edit it on windows. in the vm i have git which i use to push and pull etc. should i enable autocrlf to true? will it prevent issues for me? but i saw some ware i should set autocrlf = true in windows only. i hope someone can offer useful advice :-)

Thanks in advance.

Jya
  • 763
  • 6
  • 22

2 Answers2

6

Contrary to "Dealing with line endings", I would recommend to always set core.autocrlf to false (on Windows or any other platform):

git config --global core.autocrlf false

You don't want git to automatically changes files on a repository-wide basis without your explicit instruction.

Once you have identified specific files which requires eol management, list them in a .gitattributes file, with core.eol directives.

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • @Jayasankar, and consider studying [this `.gitattributes` file](https://github.com/mono/mono/blob/master/.gitattributes) to get further ideas. – kostix Sep 30 '13 at 17:07
3

Welcome to Git.

Here is one doc can help you set up your git conf file to handle this. Read it and practise you will love git.

Dealing with line endings

joydesigner
  • 813
  • 5
  • 11