title: How do I avoid git-svn and svn CRLF problems such as this one?
body: <p>I am using git svn and today I ran into some trouble.</p>
  
  <p>I did an <code>git svn clone</code> and worked on my project for a while. After a few days, I've pushed my work to the svn remote (<code>git svn dcommit</code>). Then I've tried to checkout the project with TortoiseSVN and see if everything is right. Unfortunately, everything was converted to Unix line endings, and VC6 failed to open the project.</p>
  
  <p>So, my git working copy was CRLF, but my svn working copy was LF. I'm assuming git converted it either during <code>git commit</code> or <code>git svn dcommit</code>.</p>
  
  <p>Am I right to assume that I can avoid all this trouble if I set <code>core.autocrlf = false</code> for my git working copy? Will this force git to leave newlines alone? Is there anything else that needs to be done to make git svn easy to use without causing problems for my coworkers?</p>
  
  <p>(It may also be interesting to mention that I have used git svn on the same machine before, without touching the settings, and this was the first time something like this happened.)</p>