Skip to content

Conversation

DotNetSparky
Copy link
Contributor

Fixes issue where the wrong parent is selected for a merge if the
correct parent consists entirely of files that were modified in earlier
changesets in the merge (it was selecting the highest "version FROM"
instead of "version TO").

I believe this could resolve #974 (it did in my specific case).

I'm having a hard time creating a unit test with a faked repository that demonstrates the original problem. If I can do that, I'll include the tests.

Tested against TFS 2017 and 2019.

Fixes issue where the wrong parent is selected for a merge if the
correct parent consists entirely of files that were modified in earlier
changesets in the merge (it was selecting the highest "version FROM"
instead of "version TO").
@Frans-Willem
Copy link

I too am having trouble with some merge-sources being incorrectly marked (usually one too low), and pulling in this changeset fixed my issue.

Thank you @DotNetSparky, and I'd like to add my vote to get this merged 👍

@pmiossec pmiossec merged commit 65130ea into git-tfs:master Apr 2, 2019
@pmiossec
Copy link
Member

pmiossec commented Apr 2, 2019

Thanks everyone!

@DotNetSparky
Copy link
Contributor Author

Thank-you @Frans-Willem and @pmiossec!

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.

Merge Changset being connected to the incorrect parent commit
3 participants