On Feb 14, 2011, at 9:57 PM, Andy Levy wrote: > Make sure that your find/sed combo is excluding .svn directories (for > some reason, I'm not able to run it on OS X). If you modify both the > "visible" file in the working copy AND the pristine copy of it, > Subversion won't detect the change.
FWIW, the find/sed combo doesn't run on OS X because 1) the find is missing the mandatory "path" argument (apparently GNU find has a non-standard extension to default path to "." if not present), and 2) standard sed has no "-i" option; again, GNU sed added it as an extension. Looks like OS X sed has the same extension, but did it slightly differently. The OS X equivalent to GNU's sed -i is sed -i "". But it would be nice if repro scripts in bug reports stuck with the standards in order to avoid these issues. (And yes, as you and others have mentioned, the reason svn status thinks that nothing has changed is because the find went into the .svn directory and made an identical change to the base copy of the file too). -- Name: Dave Huang | Mammal, mammal / their names are called / INet: k...@azeotrope.org | they raise a paw / the bat, the cat / FurryMUCK: Dahan | dolphin and dog / koala bear and hog -- TMBG Dahan: Hani G Y+C 35 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++
