On 8/9/2011 10:58 AM, 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?
In SVN (and possibly others), you have to create the branch first. In Git I still try to make the branch first, because I don't know how to move a commit to a new branch if I forget to add the new branch argument when I commit. The GUI tools I've used for SVN and Git didn't make it easy to put a commit on a new branch. In fossil I often just work and worry about branches later, sometimes several commits later, because I know it's really easy to change it. In those cases, I've usually started working on something and realized part way in that I had better branch for this--a totally stress-free realization with fossil. But sometimes I still make the branch first, because sometimes my thought process begins with "Now I'm going to start on New Feature X," and since I've just decided that, I may as well make some manifestation of my intention. I like that both ways are supported, along with the ability to make new branches after the fact. -- 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