[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/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 not have this feature enabled and wishes so, or if the feature

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user milamberspace commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-216945403 @swill conflicts fixed. Push with force done, ready to merge. --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-216889762 Please rebase this PR to fix the merge conflicts. Thanks... #1527 has been merged into 4.7 and then forward merged to 4.8 and then master. Once the merge

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user rhtyd commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-216229763 LGTM tag:mergeready --- 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

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-215698702 awesome, thank you sir. i will get this merged today... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user milamberspace commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-215671781 @swill after a new push to start a new Travis build, Travis and Jenkins are now green! You can merge the PR! :-) --- If your project is set up for it, you

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user milamberspace commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-215645435 @swill Now the Jenkins build works, but the Travis failed with: No output has been received in the last 10m0s, this potentially indicates a stalled build

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-215227139 I see another PR with the same error, so I doubt it is your PR. --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-215226141 Well Jenkins just does not like us today. Can you review the error and see if it is a valid error and try again? --- If your project is set up for it, you can

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user milamberspace commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-215215852 @swill re-done. --- 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

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-215109976 @milamberspace and again. :P sorry... --- 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

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user milamberspace commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-214791549 @swill re-push force done. --- 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

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-214789084 @milamberspace sorry to do this to you again. :( Can you force push again so we can try to get travis green. Thanks... --- If your project is set up for it, you

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user milamberspace commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-214637123 @swill It's done. --- 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

[GitHub] cloudstack pull request: L10n update 4.8 20160422

Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1515#issuecomment-214448604 Can you squash the commits for me? I will get this merged and then forward merged to master and then we can rebase the other ones to to make sure we don't have

[GitHub] cloudstack pull request: L10n update 4.8 20160422

GitHub user milamberspace opened a pull request: https://github.com/apache/cloudstack/pull/1515 L10n update 4.8 20160422 @swill the good PR for 4.8 branch. You can merge this pull request into a Git repository by running: $ git pull https://github.com/milamberspace/cloudstack