Github user mmartell commented on the issue:
https://github.com/apache/geode/pull/391
This closes #391.
---
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
Github user echobravopapa commented on the issue:
https://github.com/apache/geode/pull/391
@metatype in fact, we do have separate stories for the rest.
---
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
Github user echobravopapa commented on the issue:
https://github.com/apache/geode/pull/391
We should have separate stories/jiras for those items.
---
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 ha
Github user metatype commented on the issue:
https://github.com/apache/geode/pull/391
LGTM. There are still references to Pivotal, GemStone, and copyright stuff
that should be cleaned up.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user echobravopapa commented on the issue:
https://github.com/apache/geode/pull/391
Conflicts are removed. ready for Merge!
---
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 PivotalSarge commented on the issue:
https://github.com/apache/geode/pull/391
Done. GEODE-2348
> On 6 Feb, 2017, at 14:29, Michael Martell
wrote:
>
> Good catch that must not be used. So we should remove it. Please create a
new ticket for that.
>
Github user mmartell commented on the issue:
https://github.com/apache/geode/pull/391
Good catch that must not be used. So we should remove it. Please create a
new ticket for that.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
