Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert a commit from #5 to avoid merge conflict with bitcoin/bitcoin#22219 #41

Merged
merged 1 commit into from
Oct 3, 2021

Conversation

hebasto
Copy link
Member

@hebasto hebasto commented Sep 28, 2021

This PR reverts the "refactor: Move qwidget and qml common code into the main() function" commit (8efd330) from #5, and it allows to sync with the main repo without a merge conflict with bitcoin/bitcoin#22219.

This change allows to merge bitcoin/bitcoin#22219 without conflicts.
@promag
Copy link
Contributor

promag commented Oct 3, 2021

Tested ACK 498a318, a clean merge is possible after this.

@hebasto hebasto merged commit bd10162 into bitcoin-core:main Oct 3, 2021
@hebasto hebasto deleted the 210928-refactor branch October 3, 2021 14:16
Copy link
Member

@jarolrod jarolrod left a comment

Choose a reason for hiding this comment

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

Post-merge ACK

I would like it if we can get some other opinions on the best way to deal with sync conflicts going forward.

@hebasto
Copy link
Member Author

hebasto commented Oct 3, 2021

I would like it if we can get some other opinions on the best way to deal with sync conflicts going forward.

Yeah. To workaround that merge conflict this PR and #48 are required.

From my limited experience, the best way to deal with sync conflicts is to be a part of the main repo.

Our changes in the build system are so huge, so bumping Qt version in the main repo will cause a merge conflict for sure ((

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.

None yet

3 participants