You can set an auto-prop in the config file, but i am not sure how it reacts when the mixed endings are already there. worth trying it though. Take a look at the subversion manual but it's something like this.
[auto-props]
*.sh = svn:eol-style=LF
Of course the drawback is that you need to specify all of the file extensions - explicitly - unless you write a hook.
K.M.
Ryan Schmidt <subversion-2006Q1@ryandesign.com> wrote:
On Dec 29, 2005, at 22:56, Norbert Unterberg wrote:
> 2005/12/28, Duncan Murdoch :
>
>> I think we have fewer problems because most of the developers use
>> Unix-alikes, only a couple of us use Windows, but setting the
>> property
>> to LF and enforcing it sounds like a good idea.
>
> Is it required to enfocrce the LF policy by installing a hook? When I
> set the eol-style to LF and commit a file with different line endings
> I get a "file has inconsistent line endings" and the commit is
> aborted, isn't it?
If you want to ensure that all text files in the repository have a
particular eol-style, then yes, you must install a pre-commit hook.
Without it, nothing prevents anyone from committing a file with a
different eol-style, or with no svn:eol-style property, or worst of
all, with a mixture of line endings. The "inconsistent line endings"
error message only appears if you have set the svn:eol-style property
but the file contains a mixture of line ending styles (for example,
some lines with Unix-style LF line endings, but others with DOS-style
CRLF endings; somehow this happens all the time in our projects
because we are not yet enforcing an eol-style and are currently
relying on our developers to "do it right," of which they are clearly
incapable).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------
Yahoo! for Good - Make a difference this year.
Received on Fri Dec 30 17:08:14 2005