These files were never changed in the first place, that's the weird part.
We aren't using any local locks in the repo.
 
---- Brent



From: Johan Corveleyn <jcorvel@gmail.com>
To: webster.brent@rogers.com
Cc: "users@subversion.apache.org" <users@subversion.apache.org>
Sent: Wednesday, March 9, 2016 4:10 AM
Subject: Re: Weird Behaviour: Files reverted that didn't show up in a status --no-ignore

On Sat, Mar 5, 2016 at 12:50 AM,  <webster.brent@rogers.com> wrote:
> It was 1.8.14 client.
>
> It just said "Reverted <filename>" and the subsequent "svn status" made no
> mention of the <filename>.

Okay. I guess you cannot investigate anymore whether the content of
those files was really reverted (changed), or whether it was just some
uninteresting notification, without changing the content of the files
(for instance because the writability of the files was changed, like
Bert said: "One known case of this would be if some files were not
writable. svn revert will restore writability/non writability based on
whether a local lock is owned and/or svn:needs-lock is set, while
status doesn't report this as a modification.").

It might be interesting, in order to verify Bert's hypothesis, to
check whether those notifications happened on files with the
svn:needs-lock property or not (and whether or not the user had a lock
on them or not).

If you could reproduce this, it would be interesting to find out
whether a content change happened, or only some metadata like the
writability case.


--
Johan