2015-06-29 18:40 GMT+02:00 Joe Mistachkin:
> I've come up with an alternative implementation of this feature that I think
> is a bit simpler (see the "enhancedUndo" branch). It avoids making changes
> to anything that is unrelated to the goal at hand. I would really
> appreciate
> feedback.
Well, I tested your enhandedUndo branch, adding all the
built objects to "ignore-glob" (so I don't lose the build
during testing):
$ ./fossil extras
$ touch abc.x
$ ./fossil extras
abc.x
$ ./fossil clean
$ ./fossil undo
NEW abc.x
Then, with a >10M file:
$ ./fossil extras
$ cp [some-large file] abc.x
$ ./fossil extras
abc.x
$ ./fossil clean
WARNING: Deletion of this file will not be undoable via the 'undo'
command because the file is too big.
Remove unmanaged file "abc.x" (a=all/y/N)? y
Yes, that's exactly how I expect it to work.
Thanks!
Jan Nijtmans
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
