https://bugs.winehq.org/show_bug.cgi?id=55859
--- Comment #21 from Alex Henrie alexhenrie24@gmail.com --- (In reply to Zeb Figura from comment #20)
(In reply to Alex Henrie from comment #19)
Rebase the merge request every month until it gets more attention.
No, please don't do that. That wastes CI resources and doesn't help anything.
If the MR is not updated, people will think that it has been abandoned and that no one cares about it anymore. And if it is updated in a way that does not rerun the tests, people will be concerned that tests that were written after the patch was written might start to fail when the patch is merged. In my humble opinion, both of those considerations are worth more than than the cost to the CI server, which is probably not much if the submitter waits a full month between each rebase. However, if the Wine project leadership wants Fabian and me to stop rebasing when it's not strictly necessary, then we'll just have to defer to your preferences.
More to the point, what can we take off of your plate to give you (or whoever the appropriate reviewer might be) time to review the patch and identify specific action items to move it forward?