@@ -13,7 +13,7 @@ It then attempts to create a new commit for each commit from the original
1313It is possible that a merge failure will prevent this process from being
1414completely automatic. You will have to resolve any such merge failure
1515and run git rebase --continue. Another option is to bypass the commit
16- that caused the merge failure with git rebase --skip. To restore the
16+ that caused the merge failure with git rebase --skip. To check out the
1717original <branch> and remove the .git/rebase-apply working files, use the
1818command git rebase --abort instead.
1919
@@ -57,9 +57,9 @@ whitespace=! passed to 'git apply'
5757ignore-whitespace! passed to 'git apply'
5858C=! passed to 'git apply'
5959 Actions:
60- continue! continue rebasing process
61- abort! abort rebasing process and restore original branch
62- skip! skip current patch and continue rebasing process
60+ continue! continue
61+ abort! abort and check out the original branch
62+ skip! skip current patch and continue
6363"
6464. git-sh-setup
6565set_reflog_action rebase
@@ -72,7 +72,7 @@ ok_to_skip_pre_rebase=
7272resolvemsg="
7373When you have resolved this problem run \" git rebase --continue\" .
7474If you would prefer to skip this patch, instead run \" git rebase --skip\" .
75- To restore the original branch and stop rebasing run \" git rebase --abort\" .
75+ To check out the original branch and stop rebasing run \" git rebase --abort\" .
7676"
7777unset onto
7878strategy=
0 commit comments