A switch or setting to --perservemtime sounds like it would be easy to do, and useful.
It would leave the default behaviour for legacy reasons but allow Zoltan and others who are willing to do the make clean;make (like me) to have a useful set of file times. The nice thing would be that if you're bisecting, you can do it without the switch and get fast compilation of differences, and then you could do a fresh checkout with the switch and get the times set back to their providence. ../Dave On 17 February 2016 at 08:41, Richard Hipp <d...@sqlite.org> wrote: > On 2/17/16, Zoltán Kócsi <zol...@bendor.com.au> wrote: > > > > In fact, what I saw was that fossil didn't even do that. I checked out > > two branches (with different last mod dates) into two separate > > directories and every file had the same mtime: the current time when I > > checked them out. That is, fossil simply wrote the files from the > > database to the filesys and left the mtime as it was set by the system. > > > > That is the desired behavior, because when you do "fossil update; > make" that makefile will be looking at the mtimes and you want recent > mtimes so that the project is correctly rebuilt. > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
