Alex Riesen [off-list ref] writes:
because there are situations where it produces too much false
positives. Like when file system crawlers keep changing it when
scanning and using the ctime for marking scanned files.
This justification is good and I am very inclined to advocate for its
inclusion in 1.6.0, but any new configuration needs to be in the
documentation.
It appears there is "gui.trustmtime"; shouldn't this be called
"core.trustctime" or something?