Smart detection of renamed/moves files/folders

[hawkun]

I appreciate there has to be a limit to such an intelligence, but the most obvious changes in source could be handled smarter than trigging a complete archive deleted + copy new process.

Examples:

1. If a new file (new name) exactly matches the date, time and size (and maybe CRC) of a deleted file in the same folder in the same run, then it's the same file with a new name.

2. If a new folder (new name) ... has the same content or almost the same content (at least X% of the contained files/folders are identical) ... then it's the same folder with a new name.

You have to figure out a clever way to handle archiving. Should renames generate archived copies? Should all the corresponding file/folder names in the archive be renamed as well?

-- Håkan