Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1740
+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 your project does not have this feature
enabled and wishes so, or if the feature
Github user tibkiss commented on the issue:
https://github.com/apache/storm/pull/1740
@HeartSaVioR : Thanks for the explanation.
Created the PR for master: https://github.com/apache/storm/pull/1741
---
If your project is set up for it, you can reply to this email and have your
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1740
@tibkiss
Normally merger (or other committers) ports back commit to other branches.
Multiple PRs are needed only when there're number of conflict so would be
better to review porting
Github user tibkiss commented on the issue:
https://github.com/apache/storm/pull/1740
@HeartSaVioR : Sure, will do it shortly.
I'm wondering: shall make a PR for 1.0.x-branch too?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1740
@tibkiss Thanks for contributing. Could you also craft pull request against
master if you don't mind? It's recommended unless the patch is for specific
version.
---
If your project is set up
Github user ptgoetz commented on the issue:
https://github.com/apache/storm/pull/1740
+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 your project does not have this feature
enabled and wishes so, or if the feature
