I suspect this question has a simple and obvious answer, but I am new to Fossil and to version control. Maybe I wasn't using the correct terminology when I was searching for an answer. At this point in time, I am making sure I understand how Fossil works before I commit to it.
Here is the hypothetical situation: I have code that is maintained under Fossil. A major change request is made and many revisions occur. The change is completed but then a decision is made not to implement the change for another year. Relatively minor changes are expected to occur before the roll-out of the major change that was postponed. Under Fossil, how do I roll-back the project to the way it was before the major change was started? Can I keep the revised version of the project as a branch and then try to merge it back into a newer working-version later on? I would appreciate any advice or any links to where these issues are discussed. Thanks, Wayne Hajas Stock Assessment Analyst Fisheries and Oceans Canada Pacific Biological Station Canada 250-756-7367 wayne.ha...@dfo-mpo.gc.ca
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
