Skip to content

Conversation

@ethomson
Copy link
Member

@ethomson ethomson commented Jun 3, 2014

This introduces the ability for clients to query advanced conflict data: namely, the state of renamification that occurred leading to conflicts, and the resolved conflicts.

This includes the test repository from libgit2 that contains the types of rename conflicts that one might see (rename 1->2, rename 2->1, etc, etc).

Copy link
Member

Choose a reason for hiding this comment

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

Should this be uint like git_index_reuc_entrycount below?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yep, let me fix that.

Edward Thomson added 3 commits June 14, 2014 19:16
We're not clearing the conflicts, we're resolving them.  The
difference is that removing from the index means that the items
get moved to the REUC.  "Clearing" or "removing" (in libgit2
terminology, anyway) means that they are removed without being
resolved (or going into the REUC).
@nulltoken nulltoken added this to the v0.19.0 milestone Jun 14, 2014
@nulltoken nulltoken merged commit 413a892 into vNext Jun 14, 2014
@nulltoken nulltoken deleted the ethomson/conflicts branch June 14, 2014 20:36
@nulltoken
Copy link
Member

@ethomson Perfect PR! 💯

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.

4 participants