summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2013-12-27 14:58:08 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-12-27 14:58:08 -0800
commit2b0a564e02528e006d23e3318d0d2869fb239425 (patch)
tree76f46ae7b059ac9ca0e8b725fa67f89a3c078f16 /Documentation
parentMerge branch 'jk/rev-parse-double-dashes' (diff)
parentrebase: use reflog to find common base with upstream (diff)
downloadtgif-2b0a564e02528e006d23e3318d0d2869fb239425.tar.xz
Merge branch 'jk/pull-rebase-using-fork-point'
* jk/pull-rebase-using-fork-point: rebase: use reflog to find common base with upstream pull: use merge-base --fork-point when appropriate
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-rebase.txt10
1 files changed, 10 insertions, 0 deletions
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 94e07fdab5..2889be6bdc 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -324,6 +324,16 @@ fresh commits so it can be remerged successfully without needing to "revert
the reversion" (see the
link:howto/revert-a-faulty-merge.html[revert-a-faulty-merge How-To] for details).
+--fork-point::
+--no-fork-point::
+ Use 'git merge-base --fork-point' to find a better common ancestor
+ between `upstream` and `branch` when calculating which commits have
+ have been introduced by `branch` (see linkgit:git-merge-base[1]).
++
+If no non-option arguments are given on the command line, then the default is
+`--fork-point @{u}` otherwise the `upstream` argument is interpreted literally
+unless the `--fork-point` option is specified.
+
--ignore-whitespace::
--whitespace=<option>::
These flag are passed to the 'git apply' program