This repository has been archived by the owner on Nov 8, 2017. It is now read-only.
Add three-way merge markers support #219
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a.k.a. diff3
| These are my changes | ||
| ||||||| merged common ancestors | ||
| <<<<<<< Temporary merge branch 1 | ||
| Refer: http://stackoverflow.com/questions/16990657/git-merge-diff3-style-need-explanation |
There was a problem hiding this comment.
very complex format 😕
There was a problem hiding this comment.
Wow, yeah, that can get kind of crazy. I wonder if it can nest arbitrarily with multiple criss-cross merges... ? In that case we'd probably need some kind of recursive descent parser just to identify marked conflicts in the first place.
|
!!! That's awesome! |
|
I did it!!! 😃 |
|
|
thank you very much for this! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #9