"Thamm, Russell" <russell.th...@dst.defence.gov.au> writes:
> Any idea why svn_client_status5 is behaving so strangely? I suspect you altered all the timestamps on the working files when you copied the working copy, or perhaps the filesystems have different timestamp resolution. Running 'svn cleanup' will probably fix the problem. During write operations that modify files Subversion stores timestamp/filesize for files that are known to be unmodified. Status uses this information to avoid doing a full-text comparison on files where the timestamp/filesize match the stored values. If you do something to alter the timestamps of the working files then status will have do a full-text comparison. "Broken" timestamps get fixed by various write operations that detect the unmodified file, in particular 'svn commit'. -- Philip
