© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
While as a fellow developer I understand the point of core Wine developers of not accepting large and complex patches who, by previous experience, is unlikely to be there to maintain it in the future, thus putting the maintenance burden of this new code on the very same core Wine devs, ...
... at the same time considering the time frame of the bug, importance of the bug to a large fraction of Wine users and the fact that the solution is already well tested and used by most users of distribution packages, IMHO core developers should bite the bullet and try to review this code on its technical merits and have one of the core devs take over the responsibility for the patch, its further development and inclusion into core.
Continuing to keep this out-of-tree is guaranteed to keep the annoyance going for all parties involved.