On 2012-01-25, Michael Herndon wrote: > Stefan what did you use to check the eof of files for svn?
Pretty much a long and boring manual process. I did something like find . -name \*.cs -print0 | xargs -0 -e svn ps svn:eol-style native i.e. tried to set the eol-style property on all C# source files. This won't do anything if the property is set and tell you it has changed something in "svn status" if it the property hasn't been set before. svn will also fail if the file in question contains inconsistent line ends, this is the case for the NUnit doc files and even some of Lucene.NET sources. Repeat for all other file extension that should map to text files. > I'm setting up RAT on my local. Are there any other tools that you or ASF > recommends in general to validate releases? I think Sebb has a bunch of scripts he uses, but never bothered to look them up. If so, they'd be inside the comitters svn repo. For this release you don't even need to check line-feeds, the properties have not been set on all files. The patch I provided a while ago only applied to trunk. To me this is no reason to stop the release, in particular since most files have Windows line-ends and Prescott built the release on Windows so the files would be the same with and without svn:eol-style anyway. I intend to provide a new patch for the 3.0.3 branch once you have decided which way to go. Most likely there'll be files without license headers in that branch as well. Stefan
