Thus said Scott Doctor on Sat, 31 Oct 2015 09:45:07 -0700: > Which is why I like my process. Redundancy is good. Not dependent on > some algorithm to piece things back together. Disks are so frikkin > large now that it is not an issue to have multiple copies of the same > file. If one set gets corrupted, just use the one behind it. Fully > self contained archived snapshots not needing any program to access > it.
Do you find it easy to rationalize changes in this fashion? I suppose you can use standard tools like diff to show differences, but how to you keep track of chronological events? Have you had a look at ClearCase's MVFS (multi version file system) and VOBs? Thanks, Andy -- TAI64 timestamp: 4000000056357366 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
