On 8/9/2011 11:19 AM, Matt Welland wrote: > Note: It is annoying to me that "fossil branch new foo" won't simply > branch from the current node.
+1 > By the way, how does "update" differ from "co" in your step 2 below? If you have no edited files, they have the same effect. But if you have some edits that are not yet committed, co will fail unless called with --force, in which case it will overwrite, whereas update will merge your uncommitted changes in to the new branch's files as uncommitted changes. -- Joshua Paine LetterBlock: Web Applications Built With Joy http://letterblock.com/ 301-576-1920 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
