On Tue, 9 Aug 2011, Lluís Batlle i Rossell wrote:
If you could just tell fossil that you intend to commit to a new branch from the current workspace/checkout creating that extra commit object could be avoided without risking a commit to the wrong branch.You can *later* change the branch, after commit, as we have talked in this thread. And it's not about overwriting files, like your file save example.
True, but if your commit is to the wrong branch you're now in a race with other people. If someone performs an 'update' before you change the branch name using the GUI and push the change to the main repository your bad commit propagates. If you do that to, say, the fossil 'trunk' branch for instance someone somewhere is going to end up with your half-finished feature in their production build.....
Gé
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
