summaryrefslogtreecommitdiff
path: root/_posts/2009-09-09-removing-sensitive-data.markdown
diff options
context:
space:
mode:
authorCameron McEfee <cameron@github.com>2011-05-16 14:07:48 -0700
committerCameron McEfee <cameron@github.com>2011-05-16 16:55:31 -0700
commita483a05335c753555aba8c4529a62eb50b470028 (patch)
tree13309e7ff7b36f6020390e19067ff2251e26456d /_posts/2009-09-09-removing-sensitive-data.markdown
parentb9e8a41be8370615b233e01da697d1e6cba0b3f6 (diff)
Update files to match new style guide
Diffstat (limited to '_posts/2009-09-09-removing-sensitive-data.markdown')
-rw-r--r--_posts/2009-09-09-removing-sensitive-data.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2009-09-09-removing-sensitive-data.markdown b/_posts/2009-09-09-removing-sensitive-data.markdown
index a4e10c4..ed316ed 100644
--- a/_posts/2009-09-09-removing-sensitive-data.markdown
+++ b/_posts/2009-09-09-removing-sensitive-data.markdown
@@ -6,7 +6,7 @@ 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.
+<p span="intor">From time to time users accidentally commit data like passwords or keys into a git repo. While you can use <code>git rm</code> 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.</p>
Change your password
--------------------