Re: EOL problems in cvs2svn converted repository
From: Ryan Schmidt <subversion-2018_at_ryandesign.com>
Date: Thu, 11 Jan 2018 09:51:54 -0600
On Jan 11, 2018, at 05:43, Bo Berglund wrote:
> I have converted our CVS repositories to SVN using cvs2svn.py v 2.5.0.
If you want Subversion to perform EOL translation on a file, you must set the svn:eol-style property on that file to the desired value. There is no other way.
If you want all files with a particular name or extension to get this property when they are added to a working copy, set that up in the auto-props section of your Subversion client's file. This will apply to that client only and would need to be repeated for all clients / all users.
If using Subversion client 1.8 or later, use a repository-dictated auto-props configuration:
Auto-props only cause the property to be added to the file when the file is added to the working copy. A user can subvert auto-props, and a user can also delete the property after it was added, before or after the file was committed.
If you want to enforce that this property is used on files that need it, and/or prevent users from removing it, write a pre-commit hook that does that.
If you want all of the files you're importing from CVS that match the criteria to have the property, adjust your cvs-to-svn conversion process to arrange for that to be the case.
This is an archived mail posted to the Subversion Users mailing list.