On Wed, 09 Jan 2013 12:10:35 +0100 Gilles <[email protected]> wrote:
> Hello > > Am I correct in understanding that this is the right way to proceed to > try some new code, and either save it (whether it works or not, just > as a track-record) or discard it? > > To try some new code: > 1. Commit current code > 2. Try new code > 3. > a. if OK, commit new code : fossil commit -m "New stuff" > b. if NOK and don't care to save it, just go back to previous code: > fossil revert myfile.c > c. if NOK but want to keep track of attempt, commit and go back to n-1 > : > fossil commit -m "Failed attempt" > fossil finfo myfile.c : write down UUID (first hash) of n-1 revision > fossil revert -r UUID myfile.c If in your step 2 you add/remove/move files you "should" fossil addremove before the commit. Remember to open the repository before any change to your code, if not, when you do fossil open rep.fossil, it will note it's different from fossilized source tree and undo all your changes. > Thank you. > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users --- --- Eduardo Morras <[email protected]> _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
