Merge lp://staging/~davidc3/unity-scope-devhelp/glib-bindings-crash into lp://staging/unity-scope-devhelp
| Status: | Merged |
|---|---|
| Approved by: | Paweł Stołowski |
| Approved revision: | 31 |
| Merged at revision: | 31 |
| Proposed branch: | lp://staging/~davidc3/unity-scope-devhelp/glib-bindings-crash |
| Merge into: | lp://staging/unity-scope-devhelp |
| Diff against target: |
36 lines (+2/-14) 2 files modified
data/devhelp.scope.in (+1/-1) src/unity_devhelp_daemon.py (+1/-13) |
| To merge this branch: | bzr merge lp://staging/~davidc3/unity-scope-devhelp/glib-bindings-crash |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Paweł Stołowski (community) | Approve | ||
| PS Jenkins bot (community) | continuous-integration | Approve | |
|
Review via email:
|
|||
Commit message
Don't crash Unity bindings when building results.
Description of the change
- Don't crash Unity bindings when building results.
- Add dev, help and doc keywords
Test plan : https:/
* Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes) Yes
* Did you build your software in a clean sbuild/pbuilder chroot or ppa? Yes
* Has your component "TestPlan” been executed successfully on desktop? Yes
* If you changed the packaging (debian), did you subscribe a core-dev to this MP? N/A
* If you changed the UI, did you subscribe the design-reviewers to this MP? N/A
* What components might get impacted by your changes? None
* Have you requested review by the teams of these owning components? N/A
| PS Jenkins bot (ps-jenkins) wrote | # |
PASSED: Continuous integration, rev:31
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://