AccuRev doesn't preserve modification times, is this supported?
It is important that we maintain the original timestamps of files. We accept code drops from a third-party vendor and they need to to be integrated into our baseline. While working on a procedure for doing so, we discovered that the timestamp of the original code pulled into AccuRev changed to reflect the workspace creation date.This presents a problem for us when bringing in new code drops into AccuRev as those files end up with a new timestamp, confusing our diffs. Is it possible to maintain the original timestamps of files?
AccuRev provides an environment variable called ACCUREV_USE_MOD_TIME. If you set this environment variable, files populated to your workspace will be populated with the mod time set to the original modification time instead of the current time.
As an example on Windows, set this variable in a command shell using the command
For more information, please contact AccuRev Support.