Ryan Schmidt wrote:
> I didn't understand your reason for not wanting to use the existing
> eol enforcement technology that Subversion already has (setting
One reason is that then I would need to have these other folks working
on the project to set up their auto-props. That is about as much
trouble for me to get them to do as it is for me to get them to set up
their editors with eol conventions. If I could do one successfully
then I would be able to do the other instead. I would just set up
their editors to be newline only and be done with it.
> I would suggest that you set svn:eol-style to whatever value you like
> best (be that native or LF or CRLF) on all files that need eol
> enforcement. On each client, you set up auto-props to automatically
> set that property on those types of files, by filename extension. And
> in the server's pre-commit hook, you check that all committed files
> with whatever filename extensions do have the property set, and if
> not, exit and tell the user to set the property.
Yes, I am well aware of that process. But I was hoping to avoid it.
I think I would rather do it differently.
Thanks for your feedback anyway.
Received on 2009-03-12 08:32:38 CET