Thus said Richard Hipp on Mon, 06 Feb 2017 14:49:30 -0500: > Rather than break legacy scripts, perhaps a warning message that says > "the new branch has been created but you are not currently on that > branch - type "fossil update BRANCHNAME" to go there" or similar?
I think a warning should suffice. While I have, on occasion, also forgotten that ``fossil branch new'' doesn't automatically switch, I have gotten into the habit of using ``fossil commit --branch'' because it seems more natural, and doesn't create an extra artifact that exists solely to create a branch (though I can understand why some would prefer this method). Andy -- TAI64 timestamp: 4000000058996706 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
