[hg update] Wrong file date after an update. Is it a bug ?

[Mads Kiilerich]

William Ledoux wrote, On 10/02/2009 06:48 PM:
> It could be used, for instance, to know immediatly if a file has been
> changed before an other, or if a file from different clones at different
> revisions has been changed between these revisions: without using the
> history.
>
> Actually, "somebody" may be me.
> I have my repository, with different dates for each file. And then I
> commit (Revision 12), and then some new modifications, and I commit
> again (rev 13). If I immediatly update to revision 12, I expect my
> folder to be exactly as it was 10 seconds before, and instead of that I
> losed all the modification dates.
>
> It seems weird to me.

FWIW it seems weird to me that you rely so much on file system dates 
when you have all the information available as immutable metadata in 
Mercurial.

Mercurials focus is source code management. If you say your usecase is 
different from this then another behaviour than the one from plain 
Mercurial might be more suitable for you. That is why you will have to 
use an extension.

> Thank you for the Timestamp extension. Maybe my english is not very
> good, I understood that I had to specify each file i want to track the
> modifications dates of. Am I wrong ?

You are probably right. And yes, that might not be convenient for your 
use case. So unless you or somebody else improves the extension 
Mercurial might not be the perfect tool for you.

/Mads