Hello, I was wondering what the best or correct setting for
core.autocrlf would be when using git-svn to commit to a subversion
repository that is a windows project(ie CRLF line endings).
The documentation says that text documents are converted to LF line
endings in the repo. If you commit to subversion will if convert that
commit to have the line endings you have on your system? Or will it
use LF line endings regardless?
I would greatly appreciate if anyone could shed some light on this.
Thanks
--
Kevin
On 28. juni 2010, at 19.01, MrUnleaded wrote:
Hello, I was wondering what the best or correct setting for
core.autocrlf would be when using git-svn to commit to a subversion
repository that is a windows project(ie CRLF line endings).
The documentation says that text documents are converted to LF line
endings in the repo. If you commit to subversion will if convert that
commit to have the line endings you have on your system? Or will it
use LF line endings regardless?
"core.autocrlf=false" is the safest setting, but according to this thread:
http://kerneltrap.com/mailarchive/git/2010/3/4/24918/thread
git-svn works with core.autocrlf now. The fix was included in git 1.7.1.
To answer your question, you will end up with the correct line endings in your Subversion repository if the svn:eol-style property is set to "native" for all text files, regardless of how git is configured. If the property is not set, you should turn off autocrlf.
--
Eyvind