Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1808
@hmcl github like to truncate long messages.
```
$ git log STORM-2225
commit c9f9348e3de0917020a8c903f4c9d026b7dc6204
Author: Robert (Bobby) Evans <[email protected]>
Date: Tue Nov 29 21:39:26 2016 -0600
STORM-1997: copy state/bolt from storm-kafka to storm-kafka-client
STORM-2225: change spout config to be simpler.
STORM-2228: removed ability to request a single topic go to multiple
streams
STORM-2236: Reimplemented manual partition management on top of
STORM-2225
commit 74a77aa6494957b941df55d66ff64b6561eee4a8
Author: Robert (Bobby) Evans <[email protected]>
Date: Wed Jan 18 10:34:30 2017 -0600
Revert "Merge branch 'STORM-2236' of https://github.com/MediaV/storm
into STORM-2236"
This reverts commit e2f87c304297ce95f01708e0934c44ee385fa0bb, reversing
changes made to 00fed518d14b485e2a9e9cdd91ade3cc9d68dc8d.
```
If you really want me to squash the code change with the revert and only
reference a single JIRA in the commit messages I can. But I thought it would
be better if I am addressing 4 separate (but very closely related) JIRA I
should keep them all together.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---