diff options
| author | Junio C Hamano <junkio@cox.net> | 2006-05-16 10:35:24 +0400 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2006-05-16 10:35:24 +0400 |
| commit | 3b4fd63f72cb19288d23c9622366bbe32e55613f (patch) | |
| tree | c425a5174bf6aab06338c7da36a1764bf131753d /Documentation | |
| parent | e4e23f3a1c7734cdad60ba1274487ee6e2198de3 (diff) | |
| parent | cc120056a881101326488e3c5c2d3af2ce3a8de6 (diff) | |
Merge branch 'se/rebase'
* se/rebase:
Make git rebase interactive help match documentation.
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/git-rebase.txt | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt index 1b482abecd..08ee4aabaf 100644 --- a/Documentation/git-rebase.txt +++ b/Documentation/git-rebase.txt @@ -9,9 +9,7 @@ SYNOPSIS -------- 'git-rebase' [--onto <newbase>] <upstream> [<branch>] -'git-rebase' --continue - -'git-rebase' --abort +'git-rebase' --continue | --skip | --abort 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 -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. |