path: root/Documentation/merge-options.txt
diff options
authorJunio C Hamano <>2016-03-18 20:21:09 (GMT)
committerJunio C Hamano <>2016-04-21 18:58:51 (GMT)
commit09c2cb877a9cc0f6f25eac8d43663f4e8f3309a4 (patch)
tree0e1a2e163c79237d21c8912c6af9c92b65bf8815 /Documentation/merge-options.txt
parentde224962148c6b32ea2a6eba85578cc16d6c86c1 (diff)
pull: pass --allow-unrelated-histories to "git merge"
The previous commit said: We could add the same option to "git pull" and have it passed through to underlying "git merge". I do not have a fundamental opposition against such a feature, but this commit does not do so and instead leaves it as low-hanging fruit for others, because such a "two project merge" would be done after fetching the other project into some location in the working tree of an existing project and making sure how well they fit together, it is sufficient to allow a local merge without such an option pass-through from "git pull" to "git merge". Prepare a patch to make it a reality, just in case it is needed. Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/merge-options.txt')
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/merge-options.txt b/Documentation/merge-options.txt
index f08e9b8..dfb43d0 100644
--- a/Documentation/merge-options.txt
+++ b/Documentation/merge-options.txt
@@ -114,3 +114,11 @@ ifndef::git-pull[]
+ By default, `git merge` command refuses to merge histories
+ that do not share a common ancestor. This option can be
+ used to override this safety when merging histories of two
+ projects that started their lives independently. As that is
+ a very rare occasion, no configuration variable to enable
+ this by default exists and will not be added.