path: root/
diff options
authorSean <>2006-05-14 03:34:08 (GMT)
committerJunio C Hamano <>2006-05-14 23:28:32 (GMT)
commitcc120056a881101326488e3c5c2d3af2ce3a8de6 (patch)
treef2db202130db038b507aa8c6fa378c4977f3f3b1 /
parent975bf9cf5ad5d440f98f464ae8124609a4835ce1 (diff)
Make git rebase interactive help match documentation.
Signed-off-by: Sean Estabrooks <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to '')
1 files changed, 16 insertions, 5 deletions
diff --git a/ b/
index 9e25902..6ff6088 100755
--- a/
+++ b/
@@ -12,9 +12,10 @@ It then attempts to create a new commit for each commit from the original
It is possible that a merge failure will prevent this process from being
completely automatic. You will have to resolve any such merge failure
-and run git-rebase --continue. If you can not resolve the merge failure,
-running git-rebase --abort will restore the original <branch> and remove
-the working files found in the .dotest directory.
+and run git rebase --continue. Another option is to bypass the commit
+that caused the merge failure with git rebase --skip. To restore the
+original <branch> and remove the .dotest working files, use the command
+git rebase --abort instead.
Note that if <branch> is not specified on the command line, the
currently checked out branch is used. You must be in the top
@@ -28,6 +29,11 @@ Example: git-rebase master~1 topic
. git-sh-setup
+When you have resolved this problem run \"git rebase --continue\".
+If you would prefer to skip this patch, instead run \"git rebase --skip\".
+To restore the original branch and stop rebasing run \"git rebase --abort\".
unset newbase
while case "$#" in 0) break ;; esac
@@ -40,7 +46,11 @@ do
exit 1
- git am --resolved --3way
+ git am --resolved --3way --resolvemsg="$RESOLVEMSG"
+ exit
+ ;;
+ --skip)
+ git am -3 --skip --resolvemsg="$RESOLVEMSG"
@@ -143,4 +153,5 @@ then
git-format-patch -k --stdout --full-index "$upstream" ORIG_HEAD |
-git am --binary -3 -k
+git am --binary -3 -k --resolvemsg="$RESOLVEMSG"