As the subject says. It silently and without user consent, renamed hundreds of files, prefixing them with _corrupt_, screwing up my file base. Those files are not corrupt but simply not present in the online DB. It should either be enabled or disabled by a switch. Note that --norename command line argument was in effect. That in itself should disable this behavior.
As the subject says. It silently and without user consent, renamed hundreds of files, prefixing them with
_corrupt_
, screwing up my file base. Those files are not corrupt but simply not present in the online DB. It should either be enabled or disabled by a switch. Note that--norename
command line argument was in effect. That in itself should disable this behavior.