#9 work around windows daylight saving time errors

[Anonymous]

Windows fileservers have a strange notion of daylight
saving time. The mtime is changed one hour for files
from another daylight saving area.

The consequence is that this nice tool starts to report
many differences for files on machines with the right
understanding of daylight saving time and machines with
the wrong daylight savings implementation.

A comparison where files are accepted the same if the
mtime differs "exactly" one hour would work in most
cases.

kind regards, Gerrit Muller
gmuller@worldonline.nl

[vincent delft]

Logged In: YES
user_id=106404

I personnaly think that the user knows that DirsSync does a comparison
on mtime by default. If this behaviour occurs, or you correct or
windows environement or you can use an another comparison
mechanism : size (which is implemented).
I don't see where DirsSync must be enhanced.

I propose that if within the next 2 months we have no - detailed
enough- arguments concerning this, it will be closed.

[Nobody/Anonymous]

Logged In: NO

Allowing files to be accepted as the same if one hour difference
has merit. Exact timestamp differences occur quite often,
especially in multi-os environments, and are difficult to
workaround, predict, or detect (similar to 1 minute non-ntfs
incrementing Delft mentions elsewhere in docs)

Size differences are not acceptable alternative mechanism: one
million files, 1 hour differences between a and b location, some
files changed by just one character, so size is not different.

If you choose to implement, consider generalizing to allow
wildcard pattern matching. I may implement this and post time
permitting.