From b5a95e8c10b04c5d2add56c9d9815113149adf3f Mon Sep 17 00:00:00 2001
From: tekkub <tekkub@gmail.com>
Date: Mon, 27 Jul 2009 01:49:54 -0600
Subject: h3. --> h2.

---
 _posts/2009-06-25-moving-a-repo.textile | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to '_posts/2009-06-25-moving-a-repo.textile')

diff --git a/_posts/2009-06-25-moving-a-repo.textile b/_posts/2009-06-25-moving-a-repo.textile
index 33bdd84..d817cea 100644
--- a/_posts/2009-06-25-moving-a-repo.textile
+++ b/_posts/2009-06-25-moving-a-repo.textile
@@ -6,11 +6,11 @@ description: How to move a repo from one account to another
 categories: repos
 ---
 
-h3. Creating a new repo
+h2. Creating a new repo
 
 The first step to moving a repo is to create a new repo on the target account.  If your current repo is public, you can simply fork the repo while logged into the target account.  If the repo is private, you will need to create a new private repo on the target account to push to.
 
-h3. Creating a mirror
+h2. Creating a mirror
 
 p(. _If you forked this step is not necessary, but you may still do it for good measure._
 
@@ -22,11 +22,11 @@ git push --mirror git@github.com:mycompany/our-new-repo.git
 cd ..
 rm -rf my-old-repo</pre>
 
-h3. Reparenting forks
+h2. Reparenting forks
 
 If your original repo has forks that you wish to reparent to the new repo, please "file a support ticket":http://support.github.com/.
 *Do not delete the original repo until the reparenting is complete!*
 
-h3. Collaborators
+h2. Collaborators
 
 If your original repo had collaborators, they will not be copied.  You will need to add each user as a collaborator on the new repo.
\ No newline at end of file
-- 
cgit v1.3.1

