Hi Bart, >> is there any reason why the source code version control system trashes >> file modification dates?
> the underlying reason is to play well with "make" so that say if you > check out a file as it was two years ago and then use "make", make > will compile it because the timestamp of the file will be the current > date which is newer than the timestamp of the object file that you > still kept around. > https://git.wiki.kernel.org/index.php/Git_FAQ#Why_isn.27t_Git_preserving_modification_time_on_files.3F 1st, thanks for the explanation. 2nd, while i understand the motivation, I disagree with the 'solution', as file modification times brivide useful information when the file was last worked on. Git/subversion/... are not the only ways to look at the world. actually, when distributing source code in .ZIP files, all information of 'when was this last worked on' is lost (forever). 3rd, after thinking a while about it, here is how I would solve this problem. when extracting a file, store the 'last modification' time as is in the archive, but set 'file creation' time to 'NOW'. make xyzmake look at the younger of (file creation, last modified) time. xyzmake should be open source, anyway... this should avoid the cost of rebuilding the entire kernel, but leave modification time intact. Tom ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
