Note that =/p/condor/workspaces/your_login/CONDOR_SRC/src= contains the latest checked out Condor source. The metadata for the whole tree is stored in =/p/condor/workspaces/your_login/CONDOR_SRC/.git=. The files under =/p/condor/workspaces/your_login/CONDOR_SRC=, known as your workspace, will change as you switch from branch to branch.
+If your machine doesn't have AFS, you can have git use ssh to interact with the main repo. Your clone command would look like this:
+
+{code}
+$ git clone ssh://chopin.cs.wisc.edu/p/condor/repository/CONDOR_SRC.git
+{endcode}
+
{subsection: Cloning the main Condor manual repository}
You clone the Condor manual repository in the same way you cloned the source repository, only the central repository location is different.
@@ -78,6 +84,12 @@
If you don't like the name =CONDOR_DOC= you can feel free to rename the directory to anything you want.
+As with =CONDOR_SRC=, if your machine doesn't have AFS, you can use this clone command to interact with the main repo via ssh:
+
+{code}
+$ git clone ssh://chopin.cs.wisc.edu/p/condor/repository/CONDOR_DOC.git
+{endcode}
+
{subsection: Create names for the stable and development branches in your local repo}
Git differentiates between branches in your local repo and those in remote repos, for us that is the central Condor repo. In addition to creating entirely local branches, git lets you create local branches that track remote branches. Tracking means when something changes on the remote branch you can have those changes reflected in your repository. Having a local branch that tracks a remote branch is also the best way to commit changes to a remote branch. In general, Condor developers should always keep local branches that track the stable and development branches in the central Condor repository. Assuming the stable series is 7.0, and the development is 7.1, issue the following commands:
