From 65d7ae4ce1d731c2458d9909ec4e66a6433caf64 Mon Sep 17 00:00:00 2001 From: Ben Lynn Date: Tue, 18 Sep 2007 03:24:51 -0700 Subject: [PATCH] Reworded new sections in Git Grandmastery --- grandmaster.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/grandmaster.txt b/grandmaster.txt index ec65805..136aaea 100644 --- a/grandmaster.txt +++ b/grandmaster.txt @@ -65,7 +65,7 @@ Since this changes the history, only do this if you have yet to push your change == ... And Then Some == -Let's suppose the previous problem is ten times worse. After a lengthy session you've made a bunch of commits. But you're not quite happy with the way they're organized, and some of those commit messages could use some rewording. This is quite likely if you've been saving early and saving often. Then type +Let's suppose the previous problem is ten times worse. After a lengthy session you've made a bunch of commits. But you're not quite happy with the way they're organized, and some of those commit messages could use rewording. This is quite likely if you've been saving early and saving often. Then type $ git rebase -i HEAD~10 @@ -86,7 +86,7 @@ Next run *git-commit --amend* if you marked a commit for editing. Otherwise, run $ git-rebase --continue -Again, you can only do this if no one else has your tree. +Again, only do this if no one else has a clone of your tree. == Local Changes Last == -- 2.11.4.GIT