On Sun, Mar 23, 2014 at 1:48 PM, <to...@acm.org> wrote: > Anyway, wouldn't it nice to have an option to keep the original > timestamp? Perhaps, with a default 'now' timestamp for REVERT operations > and 'original' timestamp for UPDATE operations (at least when no specific > file set is given, and the whole tree has to be restored.) >
Fossil literally doesn't have the original timestamps - it doesn't store them. It stores the time of each commit, so the closest it can get is the timestamp of the file's checkin. As for it's timestamp-setting behaviours (or lack thereof), while it does, on some rare cases, pose a minor problem, the vast majority of the time the current behaviour is what is needed, i would argue, as is evidenced by the lack of problems people report in this regard. Make is my exclusive build platform, and i can't remember ever (since 2007) having had a problem caused by the current behaviour. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
