Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/681
---
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 is
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack/pull/681#issuecomment-130186820
Thanks for fixing these @DaanHoogland. :+1:
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
GitHub user DaanHoogland opened a pull request:
https://github.com/apache/cloudstack/pull/681
Coverity regressions per 10 aug 2015
Not all are in here, the db upgrade code seems to stay the main pitfall.
You can merge this pull request into a Git repository by running:
$ git
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/681#issuecomment-130167859
LGTM
---
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
Github user DaanHoogland closed the pull request at:
https://github.com/apache/cloudstack/pull/584
---
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 user wido commented on the pull request:
https://github.com/apache/cloudstack/pull/584#issuecomment-121177268
LGTM
---
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
GitHub user DaanHoogland opened a pull request:
https://github.com/apache/cloudstack/pull/584
Coverity regressions
three new issues pertaining to too generic exception handling
You can merge this pull request into a Git repository by running:
$ git pull
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/584#issuecomment-121183714
LGTM
---
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