diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2007-02-06 00:09:38 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2007-02-06 00:09:38 +0000 |
| commit | 42f855f6b85e5aa6ebce69b4ac12e4c8f33276a4 (patch) | |
| tree | 2e4602dc453ded05c75bcad33e72303bef2858c9 /git-rebase.txt | |
| parent | 16cf158f7b6397ada1e6d221393c66f284e15b70 (diff) | |
| download | git-htmldocs-42f855f6b85e5aa6ebce69b4ac12e4c8f33276a4.tar.gz | |
Autogenerated HTML docs for v1.5.0-rc3-80-g35ce
Diffstat (limited to 'git-rebase.txt')
| -rw-r--r-- | git-rebase.txt | 27 |
1 files changed, 25 insertions, 2 deletions
diff --git a/git-rebase.txt b/git-rebase.txt index 0cb9e1f10..977f661b9 100644 --- a/git-rebase.txt +++ b/git-rebase.txt @@ -114,6 +114,27 @@ would result in: This is useful when topicB does not depend on topicA. +A range of commits could also be removed with rebase. If we have +the following situation: + +------------ + E---F---G---H---I---J topicA +------------ + +then the command + + git-rebase --onto topicA~5 topicA~2 topicA + +would result in the removal of commits F and G: + +------------ + E---H'---I'---J' topicA +------------ + +This is useful if F and G were flawed in some way, or should not be +part of topicA. Note that the argument to --onto and the <upstream> +parameter can be any valid commit-ish. + In case of conflict, git-rebase will stop at the first problematic commit and leave conflict markers in the tree. You can use git diff to locate the markers (<<<<<<) and make edits to resolve the conflict. For each @@ -141,10 +162,12 @@ OPTIONS <newbase>:: Starting point at which to create the new commits. If the --onto option is not specified, the starting point is - <upstream>. + <upstream>. May be any valid commit, and not just an + existing branch name. <upstream>:: - Upstream branch to compare against. + Upstream branch to compare against. May be any valid commit, + not just an existing branch name. <branch>:: Working branch; defaults to HEAD. |