> You can `fossil update` and then `fossil undo`. I knew this one, but I would prefer an option that did not change the files on disk. You know, things sometimes fail, and they can fail in the middle of the operation.
This is specially true for a GUI tool that uses fossil and wants to show to the user what would happen in case of update. Would any user ever forgive the tool if it accidentally deleted one file in the course of its automatic operations? ---- Compass Ing. y Sistemas Dr. Ramon Ribo http://www.compassis.com [email protected] c/ Tuset, 8 7-2 tel. +34 93 218 19 89 08006 Barcelona, Spain fax. +34 93 396 97 46 2009/12/9 Joshua Paine <[email protected]>: > On Wed, 2009-12-09 at 23:41 +0100, Ramon Ribó wrote: >> An option that I would like to see in fossil, as it is not easy to >> perform in fossil without changing any file is a way to know what an >> update would do without actually doing it. > > You can `fossil update` and then `fossil undo`. > > -- > Joshua Paine > LetterBlock: Web applications built with joy > http://letterblock.com/ > 301-576-1920 > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
