On Fri, 16 Nov 2012 07:25:34 -0500, Richard Hipp
<[email protected]> wrote:
>There are many ways to do this. I will present one way. Others might give
>you other ideas, each with various advantages and disadvantages.
Thanks for the idea of creating a tempory branch to play with code and
either cancel or confirm changes in the trunk, instead of working on
the trunk and use revert/commit.
1. To play with code, it's safer to do this on a branch instead of the
trunk ("experimental" is just the name given to the branch):
fossil commit -m "Before playing in branch" --branch experimental
2. Edit files
3a. If you want to chuck the changes and go back to the latest
revisions from the repository:
fossil revert
fossil update trunk
3b. If you do like the changes, and want to commit them to the trunk:
fossil commit -m "Before merging branch into trunk"
fossil update trunk
fossil merge experimental
Check what states the files are in:
fossil status
Commit the changes:
fossil commit -m "Merged changes from branch into trunk"
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
