>If that's the point, then fine, do that, but then you must check out
>and manipulate the working copy exclusively from windows. It's only
>"native" to the OS doing the Subversion manipulation. So if you check
>out on Unix, you get Unix linefeeds. If you then try to edit that
>working copy on Windows, the linefeeds are Unix-native, not Windows-
>native. Hence the problem.
I missed the part in the original post where the working copy was on a
Linux drive and accessed from Windows via Samba.
The other solution is to only access the repository using the Windows
svn client or the Linux client. It seems to me it would be safer to use
native EOLS and not mix the clients. One of my co-workers uses Cygwin to
do a lot of stuff. I am not sure exactly what he does but he I end up
getting documents from him where the he has generated files using Cygwin
+ Windows tools that have weird EOLs, lines with both Unix and Windows
EOLS at the end ...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 29 18:44:16 2006