>>>>> "chromatic" == chromatic <[EMAIL PROTECTED]> writes:
chromatic> The line-ending coding standards tests can be a problem chromatic> in some cases, where Windows developers add new files chromatic> with their native format and forget to set the chromatic> svn:eol-style=native property on the files, so those chromatic> standards fail on Unix and Unix-like platforms. If it helps any: it's possible to fiddle with one's ~/.subversion/config file so that it automatically puts that property (or any property, really) on newly-added files whose names match a pattern. This isn't a foolproof solution, because it requires that every committer make this change on every box on which they hack, and I don't know if there's an equivalent mechanism for those who use git or svk. But it could be a start. Here's the relevant bits from my config file: [miscellany] ### Set enable-auto-props to 'yes' to enable automatic properties ### for 'svn add' and 'svn import', it defaults to 'no'. ### Automatic properties are defined in the section 'auto-props'. enable-auto-props = yes [auto-props] *.pl = svn:eol-style=native;svn:executable;svn:keywords=Id *.pm = svn:eol-style=native;svn:keywords=Id -- Покажи мне твой .emacs, и я скажу, кто ты. -- Russian Proverb