Default line ending property

[Frank Ronny Larsen <fr...@obexcode.com>]

Hi list,

We've set up a Subversion repository at our company and have run into a 
rather annoying problem. We work on different systems which results in 
files getting a mixture of line endings.
This can of course be solved by setting svn:eol-style to native on each 
file, but this is cumbersome and easy to forget for new files. Is there 
any way to make this setting global for the repository, so new files 
also gets this behaviour?

-Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Default line ending property

["C. Michael Pilato" <cm...@collab.net>]

Frank Ronny Larsen <fr...@obexcode.com> writes:

> Hi list,
> 
> We've set up a Subversion repository at our company and have run into
> a rather annoying problem. We work on different systems which results
> in files getting a mixture of line endings.
> This can of course be solved by setting svn:eol-style to native on
> each file, but this is cumbersome and easy to forget for new files. Is
> there any way to make this setting global for the repository, so new
> files also gets this behaviour?

At the repository level, no.  But you could have all your developers
set up the same collection of auto-props in their ~/.subversion/config
files.

Additionally, you can write a pre-commit hook which (perhaps using the
python bindings) verifies that each newly added file that matches a
particular set of patterns (*.c, *.h, etc.) also has the svn:eol-style
set, and if not, errors out.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org