On Tue, Aug 09, 2011 at 11:33:19AM -0700, Gé Weijers wrote: > > > On Tue, 9 Aug 2011, Richard Hipp wrote: > > >Change the subject: Please help me to understand why people want to create > >a new branch before adding > >changes to that branch, rather than just waiting until they check-in their > >edits? I'm not being > >sarcastic or critical here. A lot of people do this and I sincerely want to > >understand the motivation. > > If you create the branch first you cannot forget later and commit to > the wrong branch. It avoids operator error later on. If you need to > edit a file and save your changes to a copy you may do the same: > > - open the file > - use the 'save as' command to change the name > - edit for 30 minutes > - use the 'save' command. > > 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. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
