Vadim Gritsenko wrote: > upayavira wrote: > > > >@@ -31,17 +31,17 @@ > > <section id="whitespace"> > > <title>Consistent whitespace</title> > > <p> > >- Whitespace can cause big problems with CVS. If it is inconsistent, > >+ Whitespace can cause big problems with SVN. If it is inconsistent, > > then diffs are very hard to follow - actual changes become lost in > > the noise of whitespace changes. Some developers use editors that > > attempt to automatically format the whitespace. The trouble is > >- that if CVS files are inconsistent, some of those editors just > >+ that if SVN files are inconsistent, some of those editors just > > make it worse. > > </p> > ... > >@@ -75,7 +75,7 @@ > > <p> > > If you are on a UNIX system, when you receive a patch from a > > contributor on Windows then do a 'dos2unix'. If you are on a > >- Windows system, then ensure that you have a proper CVS client > >+ Windows system, then ensure that you have a proper SVN client > > (it is supposed to convert to UNIX line-endings when you commit). > > </p> > > IIUC, all of the above is not relevant for SVN as long as svn:eol-type > property is set... Can somebody confirm?
Yes it is definitely all still relevant. The committer has to clear up the line endings to be relevant to their own operating system then svn add myfile.txt svn propset svn:eol-style native myfile.txt ... or set your svn client to detect common filename extensions and automatically set that property. --David
