RE: svn status: does not notice changed file if timestamp of "new " file is older

[John Barstow <Jo...@gfsg.co.nz>]

> I don't understand.  Are you saying it's possible for the mtime to be
> unchanged, but the contents have changed?  How is that possible?

1) System clock reset (possibly by synchronizing with a time server)
2) As I recall, touch can alter the timestamp to a particular value.
3) Windows xcopy has a option to do a 'perfect' copy, with timestamps and
permissions intact - over existing files.
4) Buggy/experimental filesystem driver.
5) Some backup/restore programs will restore the original timestamp.
6) Explicitly screwing around with the filesystem APIs for proprietary
reasons.

I'm sure I can think of a few more cases if you really need them.  I've
already been bitten by cases 3 and 5, by the way, as we do a nightly import
of the production web server contents into a branch in the repository.

John C Barstow

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org