On Sat, Mar 22, 2008 at 04:54:26PM -0500, Rene Rivera wrote:
I went with:
C:\DevRoots\Boost\boost-release>find.exe . -type f -not -regex ".*[/][.]svn[/].*" -not -regex ".*\([.]bat\|[.]cmd\|[.] com\|[.]csh\|[.]m4\|[.]pl\|[.]py\|[.]sh\|configure\|rst2latex\)" -exec svn propdel "svn:executable" "{}" ";"
And then ignored the jam changes. So this should now be fixed in the release branch. I'm applying the same procedure to trunk now.
Thanks a lot. Situation improved dramatically and it was indeed not very time consuming. I checked trunk and noticed: * Many *.sh files are not marked executable. This may be OK if these files are explicitely started in a subshell or included in the current shell via ". file.sh". (These files were not touched today!) But some of these files contain also a Shebang (e.g. #!/bin/sh) http://en.wikipedia.org/wiki/Shebang_(Unix) such as tools/regression/src/run_tests.sh. Is #!/bin/sh used if the file is not executable? I doubt it. So I ask myself whether the files are really needed. * Same for *.pl, *.py, ... * tools/jam/src/boehm_gc/NT_MAKEFILE Please remove svn:executable * tools/jam/src/boehm_gc/config.sub Please re-add svn:executable So, now I stop nitpicking :-) Jens