Skip to content

Conversation

@josephfrazier
Copy link
Collaborator

From https://git-scm.com/docs/merge-options#merge-options---allow-unrelated-histories

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.

…ries`

From https://git-scm.com/docs/merge-options#merge-options---allow-unrelated-histories

> 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.
@scorphus scorphus requested review from scorphus and removed request for scorphus January 17, 2018 00:52
Copy link
Collaborator

@scorphus scorphus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for another contribution, @josephfrazier

@josephfrazier josephfrazier merged commit 027b41d into nvbn:master Jan 17, 2018
@josephfrazier josephfrazier deleted the git-merge-unrelated branch January 17, 2018 01:04
riley-martine pushed a commit to riley-martine/thefuck that referenced this pull request Dec 7, 2023
…ries` (nvbn#773)

From https://git-scm.com/docs/merge-options#merge-options---allow-unrelated-histories

> 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants