How to avoid mixed eol-styles in a svn repository

Question

Is there a best practice for preventing mixed eol-styles in a subversion repository.

I know that svn:eol-style=native can be set as an auto-prop, but I would have to ensure that it was set for all committers. I'm also reluctant to do a retrospective, repository-wide change of svn:eol-style if there is a less invasive solution.

Alastair Maw · Answer 1 · 2014-09-03T15:36:49.620

6

Note that as of SVN 1.8 you can set up auto-props for entire trees within your repository (including at the top level), which finally fixes this issue independent of client-side config.

See the following for more details:

The relevant part of the SVN 1.8 release notes
The entry on auto properties in svnbook (I'd advise you read about inheritable properties too, which is in the section immediately above)
A useful article on Apache's wiki about the subject, complete with examples for eol-style

edited Sep 03 '14 at 15:36

answered Sep 03 '14 at 12:01

Alastair Maw

5,373
1
38
50

You should specify the URL to svnbook chapter about new autoprops and svn 1.8 release notes as well. – bahrep Sep 03 '14 at 15:23
Although I somewhat assume people can use $SEARCH_ENGINE, you are right. Fixed to be more comprehensive. – Alastair Maw Sep 03 '14 at 15:31

score 5 · Accepted Answer · answered Mar 24 '10 at 17:22

5

You should use pre-commit hooks on server-side.

Here is a hook you need: http://svn.apache.org/repos/asf/subversion/trunk/contrib/hook-scripts/check-mime-type.pl

This hook will enforce users to set correct eol-style.

See svn documentation on how to use them.

Also, you can implement your own hook which will set eol-style automatically.

answered Mar 24 '10 at 17:22

uthark

5,333
2
43
59

Thanks uthark - I suspected that hooks were the answer. I'd hoped for something else since the repository isn't hosted by me but at least I'm off in the right direction – Ken Mar 25 '10 at 09:08

How to avoid mixed eol-styles in a svn repository

2 Answers2

Linked