Make git rebase interactive help match documentation.

Signed-off-by: Sean Estabrooks <seanlkml@sympatico.ca>
Signed-off-by: Junio C Hamano <junkio@cox.net>

diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 1b482abecdc2e953db1f29cb3c531f665ea8011c..08ee4aabaf74c8691a67c974bf3dca1c28cf25bc 100644 (file)
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -9,9 +9,7 @@ SYNOPSIS
 --------
 'git-rebase' [--onto <newbase>] <upstream> [<branch>]
 
 --------
 'git-rebase' [--onto <newbase>] <upstream> [<branch>]
 

-'git-rebase' --continue
-
-'git-rebase' --abort
+'git-rebase' --continue | --skip | --abort

 
 DESCRIPTION
 -----------
 
 DESCRIPTION
 -----------


@@ -23,9 +21,10 @@ not exist in the <upstream> branch.
 
 It is possible that a merge failure will prevent this process from being
 completely automatic.  You will have to resolve any such merge failure
 
 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.
 
 Note that if <branch> is not specified on the command line, the currently
 checked out branch is used.

diff --git a/git-am.sh b/git-am.sh
index 507ae4dcb9964e63143661392d7a10d7da4ef33e..33f208cb0b7a7d7bad264b41443a966a567156ff 100755 (executable)
--- a/git-am.sh
+++ b/git-am.sh
@@ -15,6 +15,10 @@ stop_here () {
 }
 
 stop_here_user_resolve () {
 }
 
 stop_here_user_resolve () {

+    if [ -n "$resolvemsg" ]; then
+           echo "$resolvemsg"
+           stop_here $1
+    fi

     cmdline=$(basename $0)
     if test '' != "$interactive"
     then
     cmdline=$(basename $0)
     if test '' != "$interactive"
     then


@@ -121,7 +125,7 @@ fall_back_3way () {
 }
 
 prec=4
 }
 
 prec=4

-dotest=.dotest sign= utf8= keep= skip= interactive= resolved= binary= ws=
+dotest=.dotest sign= utf8= keep= skip= interactive= resolved= binary= ws= resolvemsg=

 
 while case "$#" in 0) break;; esac
 do
 
 while case "$#" in 0) break;; esac
 do


@@ -157,6 +161,9 @@ do
        --whitespace=*)
        ws=$1; shift ;;
 
        --whitespace=*)
        ws=$1; shift ;;
 

+       --resolvemsg=*)
+       resolvemsg=$(echo "$1" | sed -e "s/^--resolvemsg=//"); shift ;;
+

        --)
        shift; break ;;
        -*)
        --)
        shift; break ;;
        -*)


@@ -185,7 +192,7 @@ then
 else
        # Make sure we are not given --skip nor --resolved
        test ",$skip,$resolved," = ,,, ||
 else
        # Make sure we are not given --skip nor --resolved
        test ",$skip,$resolved," = ,,, ||

-               die "we are not resuming."
+               die "Resolve operation not in progress, we are not resuming."

 
        # Start afresh.
        mkdir -p "$dotest" || exit
 
        # Start afresh.
        mkdir -p "$dotest" || exit

diff --git a/git-rebase.sh b/git-rebase.sh
index 9e259028e087e6eb33bd338855aa12f9ebb10ae9..6ff6088d187cfc54e0de0898fab555e7af319961 100755 (executable)
--- a/git-rebase.sh
+++ b/git-rebase.sh
@@ -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
 
 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
 
 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
 
 '
 . git-sh-setup
 

+RESOLVEMSG="
+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
 do
 unset newbase
 while case "$#" in 0) break ;; esac
 do


@@ -40,7 +46,11 @@ do
                        exit 1
                        ;;
                esac
                        exit 1
                        ;;
                esac

-               git am --resolved --3way
+               git am --resolved --3way --resolvemsg="$RESOLVEMSG"
+               exit
+               ;;
+       --skip)
+               git am -3 --skip --resolvemsg="$RESOLVEMSG"

                exit
                ;;
        --abort)
                exit
                ;;
        --abort)


@@ -143,4 +153,5 @@ then
 fi
 
 git-format-patch -k --stdout --full-index "$upstream" ORIG_HEAD |
 fi
 
 git-format-patch -k --stdout --full-index "$upstream" ORIG_HEAD |

-git am --binary -3 -k
+git am --binary -3 -k --resolvemsg="$RESOLVEMSG"
+