git add config repo location

git.mdwn

 # git.torproject.org and associated services
 
-# Overview
+## Overview
 
 Our git setup consists of three interdependent services:
 
@@ -11,9 +11,9 @@ Our git setup consists of three interdependent services:
 When a developer pushes to git-rw, the repository is mirrored to git and so
 made available via the gitweb service.
 
-# Regular repositories
+## Regular repositories
 
-## Creating a new repository
+### Creating a new repository
 
 Creating a new top-level repository is not something that should be done often.
 The top-level repositories are all shown on the gitweb, and we'd like to keep
@@ -76,7 +76,7 @@ Upon push, the new repository will be created. It may take some minutes to
 appear on the gitweb. Do not fear, the old list that did not yet include the
 new repository has just been cached.
 
-## Adding developers to a repository
+### Adding developers to a repository
 
 If you want access to an existing repository please have somebody who already
 has access to ask that you be added by filing a trac ticket. This should be GPG
@@ -88,7 +88,7 @@ The git team member will either add a permissions line to the configuration for
 the repository or will add a username to the group, depending on how the
 repository is configured.
 
-## Deleting accidentally pushed tags/branches
+### Deleting accidentally pushed tags/branches
 
 These requests are for a destructive action and should be signed. You should
 also sanity check the request and not just blindly copy/paste the list of
@@ -115,7 +115,7 @@ do not just give yourself `RW+` permissions for the whole repository unless you
 are feeling brave, even when someone has accidentally pushed their entire
 history of personal branches to the canonical repository.
 
-# User repositories
+## User repositories
 
 Developers who have a tpo LDAP account can request personal git repositories be
 created on our git infrastructure. Please file a ticket in Trac using the link
@@ -146,7 +146,7 @@ complicated.
 Users will have full access to their own repos and can therefore delete
 branches, tags, and perform non-fast-forward pushes.
 
-# Learning what git repos you can read/write
+## Learning what git repos you can read/write
 
 Once you have an LDAP account and have an ssh key set up for it, run:
 
@@ -158,7 +158,7 @@ and it will tell you what bits you have on which repos. The first column is who
 can read (@ for everybody, R for you, blank for not you), and the second column
 is who can write (@ for everybody, W for you, blank for not you).
 
-# Commit hooks
+## Commit hooks
 
 There are a variety of commit hooks that are easy to add for your git repo,
 ranging from irc notifications to email notifications to github auto-syncing.
@@ -166,19 +166,19 @@ Clone the gitolite-admin repo and look at the "config hooks" lines for
 examples. You can request changes by filing a trac ticket as described above,
 or just request the hooks when you first ask for your repo to be set up.
 
-## Standard Commit Hooks for Canonical Repositories
+### Standard Commit Hooks for Canonical Repositories
 
 Changes to most repositories are reported to:
 
  * the #tor-bots IRC channel (or #tor-internal for private admin repositories)
 
-## GitHub and GitLab Mirrors
+### GitHub and GitLab Mirrors
 
 Some repositories have a dedicated mailing list for commits at https://lists.torproject.org
 
 Some repositories are mirrored to https://github.com/torproject
 
-# Admin details
+## Admin details
 
 git-rw runs on `cupani.torproject.org` and runs as the git user. Users in the
 gitolite (gid 1504) group can become the git user. The gitolite installation
@@ -188,3 +188,6 @@ in the `repositories` folder there.
 Anonymous git and gitweb run on `vineale.torproject.org` and as the gitweb
 user. Users in the gitweb (gid 1505) group can become the gitweb user.
 Data for these services can be found in `/srv/gitweb.torproject.org`.
+
+The gitolite configuration is found at
+`git@git-rw.torproject.org:gitolite-admin.git` and is not mirrored to gitweb.