Make some pre blocks easier to read

_posts/2009-09-09-removing-sensitive-data.markdown

@@ -3,6 +3,7 @@ layout: default
 title: Removing sensitive data
 description: Dealing with accidentally committed passwords or other sensitive information
 categories: popular git_ninjutsu
+terminal_pres: true
 ---
 
 From time to time users accidentally commit data like passwords or keys into a git repo.  While you can use `git rm` to remove the file, it will still be in the repo's history.  Fortunately, git makes it fairly simple to remove the file from the entire repo history.
@@ -17,55 +18,67 @@ Purge the file from your repo
 
 Now that the password is changed, you want to remove the file from history and add it to the `.gitignore` to ensure it is not accidentally re-committed.  For our examples, we're going to remove `Rakefile` from the "GitHub gem":http://github.com/defunkt/github-gem repo.
 
-<pre class="terminal">[tekkub@tekBook: ~/tmp master*] $ git clone git@github.com:defunkt/github-gem.git
-Initialized empty Git repository in /Users/tekkub/tmp/github-gem/.git/
-remote: Counting objects: 1301, done.
-remote: Compressing objects: 100% (769/769), done.
-remote: Total 1301 (delta 724), reused 910 (delta 522)
-Receiving objects: 100% (1301/1301), 164.39 KiB, done.
-Resolving deltas: 100% (724/724), done.
+    tekkub@iSenberg ~/tmp master*
+    $ git clone git@github.com:defunkt/github-gem.git
+    Initialized empty Git repository in /Users/tekkub/tmp/github-gem/.git/
+    remote: Counting objects: 1301, done.
+    remote: Compressing objects: 100% (769/769), done.
+    remote: Total 1301 (delta 724), reused 910 (delta 522)
+    Receiving objects: 100% (1301/1301), 164.39 KiB, done.
+    Resolving deltas: 100% (724/724), done.
 
-[tekkub@tekBook: ~/tmp master*] $ cd github-gem/
+    tekkub@iSenberg ~/tmp master*
+    $ cd github-gem/
 
-[tekkub@tekBook: ~/tmp/github-gem master] $ git filter-branch --index-filter 'git update-index --remove Rakefile' master
-Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (266/266)
-Ref 'refs/heads/master' was rewritten</pre>
+    tekkub@iSenberg ~/tmp/github-gem master
+    $ git filter-branch --index-filter 'git update-index --remove Rakefile' master
+    Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (266/266)
+    Ref 'refs/heads/master' was rewritten
 
 This command will run the entire history of the master branch and change any commit that involved the file `Rakefile`, and any commits afterwards.  Now that we've erased the file from history, lets ensure that we don't accidentally commit it again.
 
 If you wish to retain tags you must specify `--tag-name-filter "cat"`, but note that *this will overwrite your existing tags*.
 
-<pre class="terminal">[tekkub@tekBook: ~/tmp/github-gem master] $ echo "Rakefile" >> .gitignore
+    tekkub@iSenberg ~/tmp/github-gem master
+    $ echo "Rakefile" >> .gitignore
 
-[tekkub@tekBook: ~/tmp/github-gem master*] $ git add .gitignore
+    tekkub@iSenberg ~/tmp/github-gem master*
+    $ git add .gitignore
 
-[tekkub@tekBook: ~/tmp/github-gem master+] $ git commit -m "Add Rakefile to .gitignore"
-[master 051452f] Add Rakefile to .gitignore
- 1 files changed, 1 insertions(+), 0 deletions(-)</pre>
+    tekkub@iSenberg ~/tmp/github-gem master+
+    $ git commit -m "Add Rakefile to .gitignore"
+    [master 051452f] Add Rakefile to .gitignore
+     1 files changed, 1 insertions(+), 0 deletions(-)
 
 This would be a good time to double-check that you've removed everything that you wanted to from the history.  Note that `git filter-branch` only works on one branch at a time, so you may need to perform the cleanup on other branches as well.  This could be problematic if the branch has a complex merge history.  If we're happy with the state of the repo, we need to force-push the changes to overwrite the remote repo.
 
-<pre class="terminal">[tekkub@tekBook: ~/tmp/github-gem master] $ git push origin master --force
-Counting objects: 1074, done.
-Delta compression using 2 threads.
-Compressing objects: 100% (677/677), done.
-Writing objects: 100% (1058/1058), 148.85 KiB, done.
-Total 1058 (delta 590), reused 602 (delta 378)
-To git@github.com:defunkt/github-gem.git
- + 48dc599...051452f master -> master (forced update)</pre>
+    tekkub@iSenberg ~/tmp/github-gem master
+    $ git push origin master --force
+    Counting objects: 1074, done.
+    Delta compression using 2 threads.
+    Compressing objects: 100% (677/677), done.
+    Writing objects: 100% (1058/1058), 148.85 KiB, done.
+    Total 1058 (delta 590), reused 602 (delta 378)
+    To git@github.com:defunkt/github-gem.git
+     + 48dc599...051452f master -> master (forced update)
 
 h3. Cleanup and reclaiming space
 
 While `git filter-branch` rewrites the history for you, the objects will remain in your local repo until they've been dereferenced and garbage collected.  If you are working in your main repo you might want to force these objects to be purged.
 
-<pre class="terminal">[tekkub@tekBook: ~/tmp/github-gem master] $ rm -rf .git/refs/original/
-[tekkub@tekBook: ~/tmp/github-gem master] $ git reflog expire --all
-[tekkub@tekBook: ~/tmp/github-gem master] $ git gc --aggressive --prune=1.minute
-Counting objects: 1746, done.
-Delta compression using 2 threads.
-Compressing objects: 100% (1736/1736), done.
-Writing objects: 100% (1746/1746), done.
-Total 1746 (delta 993), reused 0 (delta 0)</pre>
+    tekkub@iSenberg ~/tmp/github-gem master
+    $ rm -rf .git/refs/original/
+
+    tekkub@iSenberg ~/tmp/github-gem master
+    $ git reflog expire --all
+
+    tekkub@iSenberg ~/tmp/github-gem master
+    $ git gc --aggressive --prune=1.minute
+    Counting objects: 1746, done.
+    Delta compression using 2 threads.
+    Compressing objects: 100% (1736/1736), done.
+    Writing objects: 100% (1746/1746), done.
+    Total 1746 (delta 993), reused 0 (delta 0)
 
 Note that pushing the branch to a new or empty GitHub repo and then making a fresh clone from GitHub will have the same effect.