Yes, that is correct, but 1) Your co-developer forget to set the autoprops, so a file was committed without the property. If you set the property yourself, it will complain when the eol's in the file are not correct. If you do this at large with the svn_auto_props script, it will complain a lot. ;)
2) You get a codebase from another party and want to add this to your codebase. When you add this files and your autoprops get setted, it will also complain when the eol's in the file are not correct. So, the svn_apply_dos2unix script I have will solve this, by running dos2unix to your files, that need it, before applying the autoprops. Hth, Nick Stolwijk -----Original Message----- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Wed 1/23/2008 10:23 AM To: Maven Users List Subject: RE: End-of-line style plugin [EMAIL PROTECTED] wrote: > For what it is worth, I've adjusted the > svn_apply_autoprops.py script of subversion to apply dos2unix > to all files, which should have the svn:eol-style property > set. This clearly makes it much easier to clean your > repository or import code into your svn repository. Mind, the > new script won't have the functionality of the old script, so > you should make 2 scripts. This is unnecessary since Subversion will convert a text file on its own according the svn:eol-style setting if it is locally wrong. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
