Comment 6 for bug 238663

Ah my clock is wrong, showing the right time but "wrong".

I think the way launchad manages it now is fine, it just confused me when it
said
"in whenever". I think that its also going to be more useful having commit
time as
the last modified time which means that there is always going to be a
reliance on
the clock of the person comitting. Maybe there could be some way of warning
the
user when a nonsense time is displayed?
2008/7/10 Michael Hudson <email address hidden>:

> Adam, it does look like the clock is wrong on your machine. It's 00:01
> utc now, and your comment was nearly an hour ago.
>
> As the the wider problem, well, I think the problem is that last
> modified is a little ambiguous when it comes to branches. If it's to be
> when the branch-on-launchpad last changed, then when it was last scanned
> or last had its details changed is the right answer. It it's when the
> branch-as-a-sequence-of-revisions changed, then the time of the last
> commit is the right answer. I don't really know which is more useful.
>
> --
> Last modified date for a branch is set to when it was scanned, and not when
> committed
> https://bugs.launchpad.net/bugs/238663
> You received this bug notification because you are a direct subscriber
> of the bug.
>