Automatically Saves and Restores file timestamps for all files in the repository.
This extension is not distributed with Mercurial.
Author: Nathan Durnan
TimestampMod is an extension for Mercurial DVCS that incorporates automatic saving and restoring of the modification times of files under version control. This extension is based on an original TimestampExtension by Friedrich Kastner-Masilko <firstname.lastname@example.org> hosted at https://bitbucket.org/face/timestamp.
The intent of this extension is to ease the transition from manual file system based version control into the Mercurial DVCS world. Typically, manual file system based version control methods rely on copying and synchronizing files centered around file modification timestamp information. Under any modern VCS, this timestamp information is regarded as unimportant since the VCS manages all of the revision tracking between revision records. This means that the default behavior of most VCS is to set the file modification time to the time that the file was updated by the VCS instead of the original modification time. This is a behavior that can be confusing and lead to mistrust of the VCS by new users who are not yet familiar with VCS concepts.
Incorporating automatic timestamp saving and restoring into an extension allows Mercurial to add an extra level of comfort to those users who are more familiar with manually managing their version control via traditional file management.
This extension was developed for use with the following:
Note that only Mercurial is required for the use of this extension. However, there are some peculiarities in the code specific to use with TortoiseHg. It may also be worth noting that this extension was developed and tested only on Windows XP SP3, so functionality under other operating systems my not be one-hundred-percent reliable.
Configure your .hgrc (or mercurial.ini file for TortoiseHg) to enable the extension by adding following lines:
[extensions] TimestampMod = /path/to/TimestampMod.py
If using TortoiseHg, some of the hooks will need to be manually configured. Add entries into the hooks section of the configuration file (mercurial.ini) similar to the following::
[hooks] post-merge.TimestampMod = python:/path/to/TimestampMod.py:Hook_Post_Merge post-resolve.TimestampMod = python:/path/to/TimestampMod.py:Hook_Post_Resolve post-revert.TimestampMod = python:/path/to/TimestampMod.py:Hook_Post_Revert
Nothing further is required to make the extension work. It will set up it's own hooks that will trigger during committing and updating actions automatically.
5. Command Usage
To see a complete list of the built-in manual commands that can be executed from the command line, enter the following command:
hg timestamp_mod --help - or - hg timestamp_mod -h
The commands to manually save and restore timestamps for all files in the repository are as follows:
hg timestamp_mod -s hg timestamp_mod -r
To view the list of all timestamps recorded in the repository, use the timestamp_mod command without any arguments:
6. See also
Alternatives to this timestamp extension include:
Friedrich Kastner-Masilko's original TimestampExtension. It requires manual creation of the tracking file and manual additions to the tracking file for each file to be tracked. However, this does allow for only specific file timestamps to be tracked instead of all files in the entire repository.)
Esben Skovenborg's timestamp hook. It manages timestamps for all files in the repository automatically, but instead of the file modification time, file timestamps are restored to the timestamp associated with the last Revision involving each file in the repository. This is similar to the alternate behavior that Subversion incorporates.
Other options may also be available, but are unknown at the time this wiki was created.