path: root/Documentation/howto/revert-branch-rebase.txt
diff options
authorJunio C Hamano <>2007-02-07 18:37:03 (GMT)
committerJunio C Hamano <>2007-02-13 03:33:03 (GMT)
commit207dfa07919baba034291f1d5169f86272839d59 (patch)
treeb177a070dc2902fa269865e8d41d3a8e825c4aef /Documentation/howto/revert-branch-rebase.txt
parent07fef5fc1599d11f5750ae2440e0da6616c297b8 (diff)
Remove git-resolve.
Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/howto/revert-branch-rebase.txt')
1 files changed, 1 insertions, 8 deletions
diff --git a/Documentation/howto/revert-branch-rebase.txt b/Documentation/howto/revert-branch-rebase.txt
index d10476b..d88ec23 100644
--- a/Documentation/howto/revert-branch-rebase.txt
+++ b/Documentation/howto/revert-branch-rebase.txt
@@ -85,7 +85,7 @@ Fortunately I did not have to; what I have in the current branch
$ git checkout master
-$ git resolve master revert-c99 fast ;# this should be a fast forward
+$ git merge revert-c99 ;# this should be a fast forward
Updating from 10d781b9caa4f71495c7b34963bef137216f86a8 to e3a693c...
cache.h | 8 ++++----
commit.c | 2 +-
@@ -95,13 +95,6 @@ Updating from 10d781b9caa4f71495c7b34963bef137216f86a8 to e3a693c...
5 files changed, 8 insertions(+), 8 deletions(-)
-The 'fast' in the above 'git resolve' is not a magic. I knew this
-'resolve' would result in a fast forward merge, and if not, there is
-something very wrong (so I would do 'git reset' on the 'master' branch
-and examine the situation). When a fast forward merge is done, the
-message parameter to 'git resolve' is discarded, because no new commit
-is created. You could have said 'junk' or 'nothing' there as well.
There is no need to redo the test at this point. We fast forwarded
and we know 'master' matches 'revert-c99' exactly. In fact: