HTCondorWiki: Managing Condor Source Trees With Git

 $ git push
 {endcode}
 
-{section: Migrating old changes from a previous CVS workspace into GIT}
+{section: Creating a new development or stable series}
 
-Migrations should have already been done, but just in case any are still lingering, this documention is now at MigratingCvsWorkspaceToGit.
+The process to create a new development or stable series, i.e. new branches, is just like the process for creating branches for a share project (above). The only difference is how you decide on the branch's name. Instead of using the formula the includes some meaningful name as part of the branch name, you just update the version number. *See GitNewBranchRules for details on this.*
 
 
-{section: Creating a new development or stable series}
+{section: Migrating old changes from a previous CVS workspace into GIT}
 
-The process to create a new development or stable series, i.e. new branches, is just like the process for creating branches for a share project (above). The only difference is how you decide on the branch's name. Instead of using the formula the includes some meaningful name as part of the branch name, you just update the version number.
+Migrations should have already been done, but just in case any are still lingering, this documention is now at MigratingCvsWorkspaceToGit.
 
 {section: Merging code from the stable branch to the development branch}