> Either Visual Studio is saving files with a different EOL marker than
> what's "native" on Windows, or the EOL markers haven't been converted
> to Native yet on those files. I suspect the latter, but I don't recall
> whether setting svn:eol-style will update your working copy if you
> don't check out/update the file contents themselves (I hope that made
> sense - IOW, you can set the property, but the client won't change the
> line endings until the file contents change).
After I set the svn:eol-style property on ALL files I did update my
working copy, and TortoiseSVN actually did update all files setting the
property. The error when committing appeared after I updated my working
copy.
> Set the property again on all the files, and check out a fresh WC (or,
> for safety's sake, do this in a test repository so you don't
> accidentally mangle your production one). Then edit a couple files
> with Visual Studio and see if the same error occurs. This will
> hopefully show you which side of what I wrote above is right.
I don't see the difference between checking out a fresh WC and updating
an existing one. This is not to say that I won't try it, but simply that
I really don't know the difference :-)
> If it still happens with a fresh checkout, I would start wondering if
> Visual Studio is what's mixing your EOLs up. If that's the case, get
> VS under control, as it's the culprit.
Don't tell me. I almost only use unix :-)
Giulio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 30 15:37:41 2006