[Webkit-unassigned] [Bug 96934] Files with CRLF lineendigs without svn:eol-style=native kills git svn repositories

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=96934





--- Comment #14 from Adam Roben (:aroben) <aroben at webkit.org>  2013-02-14 14:29:53 PST ---
(In reply to comment #12)
> 1) You checkout the file with Cygwin Subversion.  The file will be LF.
> 2) You edit the file in Visual Studio and save.  The file is now CRLF.
> 3) You run svn diff, now every line shows up as a diff now.

Is this really true? I thought svn diff would take the svn:eol-style into account and not show you any extraneous diffs in this case.

> 4) You commit the file with Cygwin Subversion.  The file goes back in as LF.
>
> Alternately:
> 1) You checkout the file with Window Subversion.  The file will be CRLF.
> 2) You edit the file in Visual Studio and save.  The file is still CRLF.
> 3) You run svn diff, you only see your changes.
> 4) You commit the file with Windows Subversion.  The file goes back in as CRLF.
> 
> Both of these sound suboptimal.  Is there no way to set .gitattributes to work the same way as subversion?

According to http://svnbook.red-bean.com/en/1.1/ch07s02.html, in regards to svn:eol-style native:

> Note that Subversion will actually store the file in the repository using normalized LF EOL markers regardless of the operating system. This is basically transparent to the user, though.

So I think your (4) in each case is slightly wrong. "The file goes back in as LF" would be accurate according to the above.

So the Windows Subversion situation seems good to me. And Cygwin might be good; we just need to see how svn diff behaves.

Or am I missing something?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.