[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: converting from SVN to CVS

From: David Weintraub <qazwart_at_gmail.com>
Date: Wed, 28 Jan 2009 09:37:41 -0500

I'm not a fan of the way ANY revision control system handles the EOL
problem. In a mixed environment, we had trouble with CVS when people
edit a file in Notepad, VI on Unix, and Eclipse on various platforms.
This would also include using Cygwin.

However, I do think this is a glaring weakness in Subversion. Until
this conversation, I didn't think Subversion even handled EOL issues
unless you specifically set the svn:eol-style parameter.

It would be nice to be able to configure the server to say "If a file
ends in these suffixes, it is a text file, store the file with Unix
line endings and if you see a lone CR, a CRLF, or a LF, convert it to
LF. Then, when the client checks out the file, it would convert the
Unix line endings to whatever it wants.

Let the server clean up the line endings on commit. Let the client set
the line endings on checkout. Of course, I'd like to be able to set
exceptions like Subversion can via its svn:eol-style property, but I'd
like a sensible default way of handling this. Plus, we must have a
reasonable way to tell the version control system that something is a
binary file, so don't munge the line endings.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-28 15:38:33 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.