https://bugs.freedesktop.org/show_bug.cgi?id=82105
tommy27 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from tommy27 <[email protected]> --- the only thing you can do is: 1- dig bugzilla looking for a similar bug which was fixed by a developer, identify the committ and ask backport 2- do a retrospective bibisect of the 4.4.x branch and find the exact committ that reverted regression, and then ping the developer asking for backport this are the only way you can obtain a backport but remember that not every fix is technically backportable. regarding the status, let's ask Joel what he thinks about it. the RESOLVED WFM status is usually use in these cases, maybe we should consider adding a whiteboard status for these situations where a bug is fixed in master without knowing the committ (WFM) and we are interested in backport. we already have bibisectRequest, maybe we could have backportRequest as well. anyway the best thing is to identify the committ with one of the methods described above -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
