Re: script to detect timestamp-mismatches (inefficiency) in (1.7) working copies?

Johan Corveleyn <jcorvel_at_gmail.com> writes:

> Now, all is not lost if there are mismatches: 'svn cleanup' corrects
> the last-mod-times in the wc-metadata (for all files which are still
> identical to the pristine, the last-mod-time in metadata will be
> updated). But the problem is that users are lazy, and they won't run
> 'svn cleanup' unless they know it's necessary / beneficial. So I'd
> like to help them a bit by offering an easy way to detect if their
> working copy contains a significant amount of timestamp-mismatches.

Can that be done more efficiently than 'svn cleanup'? Perhaps what you
want is a 'svn cleanup --verbose' that reports on fixed timestamps and
redundant pristines?

-- 
Philip