sneak ab15cf32c6 Hash a file again when its mtime moved back, not only forward (closes #176) ...

scan treated a recorded file as unchanged when its size matched and its
mtime was not newer. A file replaced by other content of the same size
with an older mtime, as cp -p, rsync -a or a restore writes it, kept the
hash of the file it replaced. Any mtime difference now counts as a
change. README.md says so, and a new test covers the older mtime.

Model: opus-5-5

2026-11-11 02:29:36 +00:00

..

sfdupes

Hash a file again when its mtime moved back, not only forward (closes #176)

2026-11-11 02:29:36 +00:00