Merge lp:~aacid/unity8/run_pot_file into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Michael Zanetti on 2015-03-19 |
| Approved revision: | 1690 |
| Merged at revision: | 1694 |
| Proposed branch: | lp:~aacid/unity8/run_pot_file |
| Merge into: | lp:unity8 |
| Diff against target: |
31 lines (+4/-3) 1 file modified
po/unity8.pot (+4/-3) |
| To merge this branch: | bzr merge lp:~aacid/unity8/run_pot_file |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-03-19 | |
| Michael Zanetti (community) | 2015-03-19 | Approve on 2015-03-19 | |
|
Review via email:
|
|||
Commit Message
make pot_file
Description of the Change
* Are there any related MPs required for this MP to build/function as expected?
No
* Did you perform an exploratory manual test run of your code change and any related functionality?
N/A
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
N/A
* If you changed the UI, has there been a design review?
N/A
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1690
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
ack
* Did you perform an exploratory manual test run of the code change and any related functionality?
no... really nothing to test in here.
* Did CI run pass? If not, please explain why.
not yet...
* Did you make sure that the branch does not contain spurious tags?
yes