reset file modification time when go back in time?

[Giorgos Keramidas]

On 2007-11-06 15:43, dhruva <dhruvakm at gmail.com> wrote:
> Hi,
> Thank you for the detailed explanation you have provided. I still have
> a fundamental doubt, why do we need time stamp information to go
> across repositories through pull/push/clone?

Because this way commits done by a developer don't suddenly appear as
things which ``happened in the future'', when someone clones them.

>> Importing changesets created at a past date, with their full changelog
>> header can also mess things up.  There is at least one patch I have
>> submitted to Mercurial itself which was imported weeks after the date I
>> made it, so the changeset says the timestamp was 3 weeks ago from its
>> parent changeset!
> 
> Since we are using timestamps only to set the file's time stamp on
> update,

Are you sure we do?

The commit-time from a changeset is *NOT* used to set the modification
time of workspace files in Mercurial.

> We need to make a time stamp requirement list to decide on the
> visibility.

Not really.  Before that happens, we need to understand that we the term
'timestamp' in everything you have written so far refers to at least two
different things:

  * The commit time recorded as part of a changeset

  * The modification time of a file in the workspace area

Which one of the two are you interested in, and what is it in the
current behavior that you would like to change?