Merge lp://staging/~3v1n0/ubuntu/vivid/freetype/multithread-safe into lp://staging/ubuntu/vivid/freetype
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 63 | ||||
Proposed branch: | lp://staging/~3v1n0/ubuntu/vivid/freetype/multithread-safe | ||||
Merge into: | lp://staging/ubuntu/vivid/freetype | ||||
Diff against target: |
2133 lines (+2113/-0) 3 files modified
debian/changelog (+7/-0) debian/patches-freetype/multi-thread-violations.patch (+2105/-0) debian/patches-freetype/series (+1/-0) |
||||
To merge this branch: | bzr merge lp://staging/~3v1n0/ubuntu/vivid/freetype/multithread-safe | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Dmitry Shachnev | Needs Information | ||
Review via email: mp+247373@code.staging.launchpad.net |
Description of the change
Backported patches coming from this patchset [1] that has been just merged upstream [2] and that fixes huge multithread violations that are causing crashes in a lot of places in the upper stack.
Here [3] you can read more details about this patch.
[1] https:/
[2] http://<email address hidden>
[3] http://<email address hidden>
For being precise, this patch includes the changes merged in commits:
http://
http://
http://
http://
http://
http://
http://
http://
http://
http://
http://
http://
http://
http://
http://
http://
http://
http://
Can we just update to ≥ 2.5.6, instead of cherry-picking a ton of commits?