On Mon, Dec 15, 2014 at 2:01 PM, Stephan Beal <[email protected]> wrote: > > On Mon, Dec 15, 2014 at 7:49 PM, Petr Ferdus <[email protected]> wrote: >> >> Something similar like taking ls -al of all files in repository, >> redirecting output to file and versioning that file. Except this would >> happen automatically on commit or some other command. >> Such information could be displayed in "File Tree" menu or for file >> restoring purposes. >> > > In any case: because the timestamps of files is computed, not stored, and > because the timestamp of a manifest can edited (well, amended), a static > view of the data might someday become incorrect if a timestamp adjustment > is made on a checkin after the fact. >
The "static view" won't actually become incorrect. it simply records the m-times the files had when a given commit was made. that information might be useful for documentation purposes. Some VCSs do record those m-times, usually providing an option to set m-times to the saved values when files are fetched from the VCS. For build purposes, it is often more convenient for files to have the m-time of when they were fetched. That way, an incremental build is possible. But, I long ago stopped to trying mess with VCS m-time settings and started just always doing a "make clean" after fetching anything. Otherwise, the only reason I would care about the m-times stored in a VCS would be for generating reports.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
