D25299: Composite without timer on swap events
David Edmundson <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kwin |
|---|---|
| Message-ID | <[email protected]> |
davidedmundson added a comment. Urgh, no. I had an unsubmitteed comment for moving forwards. This patch takes 1 step backwards in order to eventually go 2 steps forward. A perfectly sensible strategy, but I don't like having master that goes backwards without a completely solid plan to go forward. The risk of things not getting completed and us releasing something that makes things worse are too high. But I don't want to hold this up, so in order to resolve this in a way where we can all keep moving forward, I have a proposal: - I'll approve it, but we merge this commit as-is into a feature branch, rather than master - We can then then do the next review based on that branch - We can work, hack, rebase and submit reviews on that branch (and vlad and I can help run and rebase it and whatever) - Master stays "sunny" Then when we have the vsync timer we can merge this all into master. Everyone wins. REPOSITORY R108 KWin REVISION DETAIL https://phabricator.kde.org/D25299 To: romangg, #kwin Cc: kwin, davidedmundson, zzag, LeGast00n, The-Feren-OS-Dev, sbergeron, jraleigh, fbampaloukas, GB_2, mkulinski, ragreen, jackyalcine, iodelay, crozbo, bwowk, ZrenBot, ngraham, alexeymin, himcesjf, lesliezhai, ali-mohamed, hardening, romangg, jensreuterberg, abetts, sebas, apol, ahiemstra, mart