Skip to content

Conversation

@mattst88
Copy link
Contributor

Unsure what the behavior should be. Currently the result depends on the order of the commits being merged. maybe this is reasonable? Seems a bit scary.

…me keyword

Unsure what the behavior should be. Currently the result depends on the
order of the commits being merged. maybe this is reasonable? Seems a bit
scary.
@mattst88
Copy link
Contributor Author

(The new test is expected to fail)

cc: @thesamesam

I'm thinking that maybe the right thing to do is: nothing. If we're merging commits that modify the same keyword, we should leave a real conflict in the file.

Copy link
Member

@thesamesam thesamesam left a comment

Choose a reason for hiding this comment

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

Yeah, I think you're right -- we don't want to resolve it. If someone added "-x86" because it turns out to be broken but I have some generic AT commit adding x86 because a compile test passed and it has no testsuite, I don't want that fixed up for me.

We could maybe have an aggressive mode or something but I don't think there's much of an audience for that

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