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

[William Ledoux]

On Fri, Oct 2, 2009 at 5:59 PM, Mads Kiilerich <mads at kiilerich.com> wrote:

> You are right. That is intentionally how it is. In a DVCS _you_ are the
> center of the universe,

so what matters is when a file arrived on your harddisk, not the date when
> somebody made a change in their local repo.
>

Thank you for the quick answer !

It may not matters much to know when some guy made a modification to a file,
but at least it is an information, and I think it matters MORE than having
all files to the date of today, which is NO information since I already know
it.
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.

So similarly, when I pull modifications, the modification date should be the
date when I pulled it, not the date of the push ?

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 ?

William.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20091002/66395fa8/attachment-0001.html>