On Wed, Mar 2, 2016 at 9:53 PM, <webster.br...@rogers.com> wrote: > We are running VisualSVN 1.9.3 server on a Windows box and a user's > workspace is on a Centos6.5 Linux box. > He had just done a "svn update" and the build failed. No conflicts as far > as I can tell. The "svn status" showed the build artifacts and his modified > files. As a suggestion, he would "svn revert -R ." all his changes. During > the revert, it showed numerous other SVN element(cpp & h) files being > reverted that he never touched and the "svn status --no-ignore" never > showed. We tried reproducing it but no luck. > > I'm in the process of switching over a bunch of "old", hardened Clearcase > folks to SVN so this little weirdness is never good to see.
Would still be unexpected / weird, but: is it possible that those files were not really changed, but that 'revert' simply generated unnecessary notifications (showing 'reverted file X' for files that weren't really changed)? You didn't mention the version of svn client. Maybe it's a notification bug in the client that's already fixed? -- Johan
