Skip to content

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 ((

johnny9 pushed a commit to johnny9/bitcoin-core-app that referenced this pull request Jul 4, 2025
… conflict with bitcoin/bitcoin#22219

482aab3 Revert 8efd330d54e75e4a5de36278299b5227e4e5bfdf (Hennadii Stepanov)

Pull request description:

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

ACKs for top commit:
  promag:
    Tested ACK 482aab3, a clean merge is possible after this.

Tree-SHA512: b1d3708a20f36b81225a3c25963dbc32c3a33e54a795184cfea5b4af9c98ecd68cee8d297e94cced3f118aed738bafd4312536d62a445d09626d7fad613a2323
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.

3 participants