Appeal to respect the development history and time tracking

[Arne Babenhauserheide]

Am Dienstag, 25. August 2015, 17:57:15 schrieb Gregory Szorc:
> 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.

I do not read the OPs post as requiring security against potential
attackers, so I think you’re trying to be too perfect here, impeding
on a solution which would solve the usecase at hand.

The date of the tip-most commit which changed the file should be
completely sufficient for most tasks. By going through the whole
history it would also be possible to get the most recent date at which
each file was changed. It shouldn’t even be too expensive: Building a
dictionary of path+date and only updating the date when it’s larger
than the existing date.

Best wishes,
Arne
--
Celebrate with ye beauty and gather yer friends for a Pirate Party!
    → http://1w6.org/english/flyerbook-rules#pirate-party ←

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 299 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20150827/6da2362f/attachment.asc>