@@ -13,7 +13,7 @@ It then attempts to create a new commit for each commit from the original
13
13
It is possible that a merge failure will prevent this process from being
14
14
completely automatic. You will have to resolve any such merge failure
15
15
and 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
17
17
original <branch> and remove the .git/rebase-apply working files, use the
18
18
command git rebase --abort instead.
19
19
@@ -57,9 +57,9 @@ whitespace=! passed to 'git apply'
57
57
ignore-whitespace! passed to 'git apply'
58
58
C=! passed to 'git apply'
59
59
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
63
63
"
64
64
. git-sh-setup
65
65
set_reflog_action rebase
@@ -72,7 +72,7 @@ ok_to_skip_pre_rebase=
72
72
resolvemsg="
73
73
When you have resolved this problem run \" git rebase --continue\" .
74
74
If 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\" .
76
76
"
77
77
unset onto
78
78
strategy=
0 commit comments