[GitHub] cloudstack pull request: L10n update 4.8 20160127

2016-04-22 Thread milamberspace
Github user milamberspace closed the pull request at: https://github.com/apache/cloudstack/pull/1375 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] cloudstack pull request: L10n update 4.8 20160127

2016-04-22 Thread milamberspace
Github user milamberspace commented on the pull request: https://github.com/apache/cloudstack/pull/1375#issuecomment-213496639 Close, replace by #1515 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

[GitHub] cloudstack pull request: L10n update 4.8 20160127

2016-04-22 Thread swill
Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1375#issuecomment-213415473 @milamberspace can you close and reopen this against the 4.8 branch. It is currently opened against master. Thanks... --- If your project is set up for it, you

[GitHub] cloudstack pull request: L10n update 4.8 20160127

2016-04-20 Thread milamberspace
Github user milamberspace commented on the pull request: https://github.com/apache/cloudstack/pull/1375#issuecomment-212325281 @swill I've just rebase from 4.8 branch update the L10N files and push --force this PR. The PR #1376 is not linked with this PR. cc @koushik-das

[GitHub] cloudstack pull request: L10n update 4.8 20160127

2016-04-19 Thread swill
Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1375#issuecomment-211918463 This one looks like it will have merge conflicts with #1376. @milamberspace should I first merge #1376 and then have you rebase this PR and fix the conflicts before

[GitHub] cloudstack pull request: L10n update 4.8 20160127

2016-04-19 Thread koushik-das
Github user koushik-das commented on the pull request: https://github.com/apache/cloudstack/pull/1375#issuecomment-211860481 @swill Again UI changes related to l10n. I think these can be merged. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] cloudstack pull request: L10n update 4.8 20160127

2016-03-19 Thread bvbharatk
Github user bvbharatk commented on the pull request: https://github.com/apache/cloudstack/pull/1375#issuecomment-198122730 ### ACS CI BVT Run **Sumarry:** Build Number 108 Hypervisor xenserver NetworkType Advanced Passed=105 Failed=13 Skipped=4

[GitHub] cloudstack pull request: L10n update 4.8 20160127

2016-01-27 Thread milamberspace
GitHub user milamberspace opened a pull request: https://github.com/apache/cloudstack/pull/1375 L10n update 4.8 20160127 cc @remibergsma @bhaisaab @DaanHoogland You can merge this pull request into a Git repository by running: $ git pull