Daniel Kulp wrote: > Roy T. Fielding wrote: > > > Similarly, I'm seeing a number of files that show up with every > > > single line changed, when AFAICT all that should change is the > > > removal of a single line from the list of projects. What's up with > > > that? > > > > Do you really want to hear my opinion of Subversion's lack of > > a centralized default for svn:eol-style=native? > > Maybe you could implement a variation on svn propget -R that > > returns the path to all files the do not have svn:eol-style=native. > > *sigh* I'll just use a find pipe. > > For tuscany/cxf/qpid, I kind of wrote a script that will go through > everything and add a "proper" set of props: > > http://svn.apache.org/repos/asf/incubator/tuscany/java/etc/set_svn_properties.sh
Thanks. It is a pity that each project needs to grapple with such svn management. On xml-based projects there are problems due to many weird filename extensions, so i use a different approach with https://svn.apache.org/repos/private/committers/tools/report_svn_text.pl It scans for text files and reports which do not have "svn:eol-style native". AFAIK one also needs to fix the line-endings to be appropriate for the local operating system. So it is probably a manual job to report and fix. This type of thing wastes a lot of time for open source. We have tried to encourage ASF committers to configure their svn client: http://apache.org/dev/version-control.html#https-svn The SVN FAQ mentions the possibility of (rather drastic) pre-commit hook. Perhaps we should (/me ducks). Or perhaps we should set up a regular (monthly?) job that scans each project trunk and reports such issues. -David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
