From 2575b8a597d3febb0088d02fb64214c3dbd5fd57 Mon Sep 17 00:00:00 2001 From: Cameron McEfee Date: Mon, 16 May 2011 10:23:11 -0700 Subject: bring documentation in line with new styles --- _posts/2010-01-29-rebase.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '_posts/2010-01-29-rebase.markdown') diff --git a/_posts/2010-01-29-rebase.markdown b/_posts/2010-01-29-rebase.markdown index fd7b9c7..8fce0f6 100644 --- a/_posts/2010-01-29-rebase.markdown +++ b/_posts/2010-01-29-rebase.markdown @@ -7,7 +7,7 @@ categories: everyday_git One often overlooked feature of git is the `git rebase` command. Rebase allows you to easily change a series of commits, reordering, editing, or squashing commits together into a single commit. -_It is considered bad practice to rebase commits which you have already pushed to a remote repo. Doing so may invoke the wrath of the git gods... you have been warned._ +It is considered bad practice to rebase commits which you have already pushed to a remote repo. Doing so may invoke the wrath of the git gods... you have been warned. So, you've cloned a repository, and hacked away at it; separated it into logical chunks, and it's now ready to submit! -- cgit v1.3.1