HTCondorWiki: Managing Condor Source Trees With Git

 
 This document explains common source code management tasks for Condor, and how you can accomplish them with the git tools.
 
-As of August 2011, Condor's source and manual are in one repository.  The source and manual reside in =/p/condor/repository/CONDOR_SRC.git=, and the externals are in =/p/condor/repository/CONDOR_EXT.git=.
-
-Branching and merging of the source and manual can happen at different times, just like with CVS.  The use of externals is different.  Externals will now be branched, instead of having CVS modules (form CVSROOT/modules) to checkout just a portion of the entire externals repository.
+As of August 2011, Condor's source and manual are in one repository.  The source and manual reside in =/p/condor/repository/CONDOR_SRC.git=,
 
 {section: Preliminary setup}
 
@@ -91,24 +89,7 @@
 # git limitations
 
 
-# And if you have a clone of the manual too
-$ cd /p/condor/workspaces/your_login/CONDOR_DOC
-$ git branch V7_0-branch origin/V7_0-branch
-{endcode}
-
-The =CONDOR_EXT.git= repository is handled a bit differently. It does not treat its primary, "master", branch as the development series by default. Instead you will need to create a =V7_1-branch= from the central repository's =V7_1-branch=. Like so:
-
-{code}
-$ cd /p/condor/workspaces/your_login
-$ git clone /p/condor/repository/CONDOR_EXT.git
-
-$ cd CONDOR_EXT
-
-$ git branch V7_0-branch origin/V7_0-branch
-$ git branch V7_1-branch origin/V7_1-branch
-{endcode}
-
-And that's all you need!  You are now good to go.  It wouldn't hurt to clean up any unreachable objects nows, it doesn't take long, and it makes the repo smaller and faster.  You can run this in both your =CONDOR_SRC.git= repository or your =CONDOR_DOC.git= repository:
+You are now good to go.  It wouldn't hurt to clean up any unreachable objects nows, it doesn't take long, and it makes the repo smaller and faster.
 
 {code}
 $ git gc --prune