reset file modification time when go back in time?

[Marcin Kasperski]

> The problem I face when I change between branches is the
> modification in the file timestamps. Whenever I switch a branch, the
> build system recompiles the whole stuff.

First: it would be bad idea if it did not. Imagine for example that
you have compiled blahblah.o from blahblah.c. Now you switch to the
*older* branch where is *older* version of blahblah.c. Would mercurial
reset the blahblah.c date back, it would *not* be recompiled. You
would have too new object file, which not necessarily matches the
rest.

True solution is possible in the build system, not in mercurial.
You may for example take a look at makepp. It is able to use
md5 checksums instead of timestamps to detect what changed...

----------------------------------------------------------------------------
| Marcin Kasperski   | 1 woman, 9 months = one baby. But we have 1 month, so
| http://mekk.waw.pl |    let's take 9 women! (common management practice)
----------------------------------------------------------------------------