Hello, Much nicer:
fossil add kk.cc fossil commit -m "v1" (some failed changes) fossil commit -m "failed attempt" --branch failed_attempt fossil update trunk (some changes) fossil commit -m "good" ---- 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 2013/1/9 Gilles <[email protected]>: > 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 > > Thank you. > > _______________________________________________ > 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
