On Sat, Apr 19, 2014 at 7:53 PM, <to...@acm.org> wrote: > Fine, but I don’t think this would require a multi-level undo stack. A > simple flag to indicate at the >
No, it wouldn't require much actual effort, it just requires that revert check for changes before trying to revert. completion of any command if anything has changed (i.e., files written, > deleted, or renamed) during its execution would be enough to decide whether > to clear the one-level stack or leave it as is. No time-consuming checks > would be needed, IMO, if setting of the flag is placed in the correct > places. > It's not just a flag - fossil has to compare everything in the checkout file list with the filesystem. At the very minimum, it will check their timestamps, and it may perform an SHA1 has on the contents of the file (that's the expensive part, reading and hashing the file, and it's all done in memory). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
