On 07.04.2015 00:17, Eric Melski wrote: Hi,
> This problem is relatively common when using an SCM system that > preserves *checkin* time on files rather than *checkout* time. I'd consider that a misbehavious of the SCM (IMHO, that's the reason why Git does not track the mtime). From the filesystem perspective, the mtime represents the time when the actual file was changed in the filesystem. So, resetting the mtime from some SCM repo actually is tricking the filesystem - pretty obvious that the mtime then isn't reliable anymore. > ClearCase > does this in various configurations, and Perforce will if your client > spec has "modtime" set. I'm sure other SCM systems can be setup this > way too. The correct solution is to configure the SCM correctly (so it does not artificially manipulate the mtime). cu -- Enrico Weigelt, metux IT consulting +49-151-27565287 _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
