Github user anshul1886 commented on the pull request:
https://github.com/apache/cloudstack/pull/351#issuecomment-131724787
@remibergsma Either we have to squash all commits to one commit or leave it
as it is. In squashing all commits to one I will put all the relevant messages.
These commits don't have in order dependency. So what would you prefer one
commit or leave it as it is?
Implementation have very little impact in core CloudStack so will not
affect functionality of other Hypervisors. Also I have done testing on my end
to make sure everything works fine after these commits.
Existing unit tests will be able to identify the issues in management
server code.
---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
