Skip to content

Commit b5e104a

Browse files
committed
Merge branch 'mz/doc-rebase-abort' into maint
* mz/doc-rebase-abort: rebase: clarify "restore the original branch"
2 parents 22d9b79 + 5960bc9 commit b5e104a

File tree

2 files changed

+11
-7
lines changed

2 files changed

+11
-7
lines changed

Documentation/git-rebase.txt

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ with a different commit message or timestamp will be skipped).
4545
It is possible that a merge failure will prevent this process from being
4646
completely automatic. You will have to resolve any such merge failure
4747
and run `git rebase --continue`. Another option is to bypass the commit
48-
that caused the merge failure with `git rebase --skip`. To restore the
48+
that caused the merge failure with `git rebase --skip`. To check out the
4949
original <branch> and remove the .git/rebase-apply working files, use the
5050
command `git rebase --abort` instead.
5151

@@ -232,7 +232,11 @@ leave out at most one of A and B, in which case it defaults to HEAD.
232232
Restart the rebasing process after having resolved a merge conflict.
233233

234234
--abort::
235-
Restore the original branch and abort the rebase operation.
235+
Abort the rebase operation and reset HEAD to the original
236+
branch. If <branch> was provided when the rebase operation was
237+
started, then HEAD will be reset to <branch>. Otherwise HEAD
238+
will be reset to where it was when the rebase operation was
239+
started.
236240

237241
--skip::
238242
Restart the rebasing process by skipping the current patch.

git-rebase.sh

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ It then attempts to create a new commit for each commit from the original
1313
It is possible that a merge failure will prevent this process from being
1414
completely automatic. You will have to resolve any such merge failure
1515
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
1717
original <branch> and remove the .git/rebase-apply working files, use the
1818
command git rebase --abort instead.
1919
@@ -57,9 +57,9 @@ whitespace=! passed to 'git apply'
5757
ignore-whitespace! passed to 'git apply'
5858
C=! 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
6565
set_reflog_action rebase
@@ -72,7 +72,7 @@ ok_to_skip_pre_rebase=
7272
resolvemsg="
7373
When you have resolved this problem run \"git rebase --continue\".
7474
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\".
7676
"
7777
unset onto
7878
strategy=

0 commit comments

Comments
 (0)