You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by karuturi <gi...@git.apache.org> on 2017/04/07 04:25:06 UTC

[GitHub] cloudstack pull request #2032: CLOUDSTACK-9783: corrected the version number...

GitHub user karuturi opened a pull request:

    https://github.com/apache/cloudstack/pull/2032

    CLOUDSTACK-9783: corrected the version number in metrics pom

    master is broken after fwd-merging metrics PR #1944 from 4.9
    This is due to the incorrect parent version number in the metrics pom.
    Corrected the same to reflect master version number.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Accelerite/cloudstack master-fix-after-1944

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/2032.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2032
    
----
commit e1c76dcc235fd350f87725adaf359619331db278
Author: Rajani Karuturi <ra...@accelerite.com>
Date:   2017-04-07T04:22:27Z

    CLOUDSTACK-9783: corrected the version number in metrics pom
    
    master is broken after fwd-merging metrics PR #1944 from 4.9
    This is due to the incorrect parent version number in the metrics pom.
    Corrected the same to reflect master version number.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #2032: CLOUDSTACK-9783: corrected the version number...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/cloudstack/pull/2032


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #2032: CLOUDSTACK-9783: corrected the version number in met...

Posted by koushik-das <gi...@git.apache.org>.
Github user koushik-das commented on the issue:

    https://github.com/apache/cloudstack/pull/2032
  
    LGTM. Build is broken due to this.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #2032: CLOUDSTACK-9783: corrected the version number in met...

Posted by rhtyd <gi...@git.apache.org>.
Github user rhtyd commented on the issue:

    https://github.com/apache/cloudstack/pull/2032
  
    Thanks @karuturi I usually rebuild CloudStack when forward merging PRs to ensure they don't break the forward-branches


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #2032: CLOUDSTACK-9783: corrected the version number in met...

Posted by DaanHoogland <gi...@git.apache.org>.
Github user DaanHoogland commented on the issue:

    https://github.com/apache/cloudstack/pull/2032
  
    LGTM, checked the source
    $ grep -r 4.9.3.0
    no hits


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---