Appeal to respect the development history and time tracking

[Roger Gammans]

On Tue, 2015-08-25 at 17:57 -0400, Gregory Szorc wrote:


> What you really would want to use is "push times." But that's not a
> concept that exists in core Mercurial. Even if it did, you have to
> choose which remote's times to use. Even if you did that, computer
> clocks aren't reliable and are prone to skew and other weirdness. Yes,
> even on servers.
> 
> 
> This feature cannot be implemented in a manner that would be
> reasonable. The best Mercurial could do is set mtimes such that the
> times from commit N+1 are newer than commit N. But the actual times
> would not correspond to commit/push times. At that point, what's the
> point?

If the OP really wants this, there is the option of using metastore 
( https://github.com/przemoc/metastore ) which can write the file
metadata to it own file . This files content can be tracked with
mercurial itself. Then the metastore can be used to restore the
metadata.

In this case the file meta data is even versioned - although I'd prefer
a more text like format so diffs where meaningful .

Extra points for doing it automatically with commit /update hook.

Where I use this is to build an revision control tools to create
auditable log of deployments with a revision control system.

-- 
Roger Gammans <roger at gammascience.co.uk>