Re: CRLF problems with Git on Win32

From: Peter Harris <peter@peter.is-a-geek.org>
Date: Jan 8, 2008, 13:07 UTC
Message-ID: <eaa105840801080507j1b748fy6fdff8b240cf8c33@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.64.0801081150010.25629@ds9.cixit.se>

On Jan 8, 2008 5:56 AM, Peter Karlsson <peter@softwolves.pp.se> wrote:

Show 10 quoted lines

> Thomas Neumann:
>
> > as a user, I expect a SCM to only modify a file when I have
> > explicitly asked it to do so.
>
> As a user, I exepect things to just work. With RCS/CVS/Subversion, it
> does, because it differentiates between text files (internally encoding
> NLs with "LF", but I couldn't care less what it uses there) and binary
> files (which it doesn't change). With git it currently doesn't since it
> treats everything as binary files.

Actually, Subversion does the Right Thing, and treats everything as a binary file until and unless you explicitly set the svn:eol-style property on each file that you want it to mangle.

Maybe you set up Subversion auto-props and forgot about it? That would be almost (but not really) like setting autocrlf=true in your global git config.

Peter Harris