HTCondorWiki: Managing Condor Source Trees With Git

-See also:
-<ul>
-<li><a href="http://nmi.cs.wisc.edu/node/1436">Random Git Wisdom</a>
-</ul>
+See also: {drupalnode: 1436}
 
-<h1>Add <code>/unsup/git/bin</code> to your path</h1>
+*Add this to your path:*
+{code}/unsup/git/bin{endcode}
 
-<h1>Gitweb, think bonsai, is available at <code>http://bonsai.cs.wisc.edu/gitweb/gitweb.cgi</code></h1>
+*Gitweb, think bonsai, is available at:*
+{code}http://bonsai.cs.wisc.edu/gitweb/gitweb.cgi{endcode}
 
-<h1>Managing Condor source, manual and externals trees with GIT</h1>
+{section: Managing Condor source, manual and externals trees with GIT}
 
 This document explains common source code management tasks for Condor, and how you can accomplish them with the git tools.
 
-<p>
-As of the switch to git, Condor's source, manual and externals live in different repositories.  The source resides in <code>/p/condor/repository/CONDOR_SRC.git</code>, the manual in <code>/p/condor/repository/CONDOR_DOC.git</code>, and the externals in <code>/p/condor/repository/CONDOR_EXT.git</code>.
 
-<p>
+As of the switch to git, Condor's source, manual and externals live in different repositories.  The source resides in {quote: /p/condor/repository/CONDOR_SRC.git}, the manual in {quote: /p/condor/repository/CONDOR_DOC.git{endcode}, and the externals in {code}/p/condor/repository/CONDOR_EXT.git{endcode}.
+
+
 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.
 
 <h1>Preliminary setup</h1>