Hi all, one of the smaller issues when comparing cvs and fossil is the handling of mtime on checkout and update. If you checkout a new working copy with CVS, all files will get the time of last commit as mtime. This is highly useful as it makes it very easy to find out the age of a file when browsing a directory. On update, cvs picks the start time as new mtime. That way, files that are modified get a new timestamp and dependency tracking e.g. with make works. Is there a good reason to not adopt this behavior for fossil?
Joerg _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
