Github user pivotal-jbarrett commented on the issue:

    https://github.com/apache/geode-native/pull/106
  
    @gregt5259 This is a solution to the problem but not the solution we as 
committers are comfortable committing as it directly conflicts with the correct 
change, which is to use type safe durations rather than magic number math and 
system wide properties to create a confusing array of time values.
    
    If you want this change sooner than later you could implement it using 
std::chrono::duration as outlined in GEODE-3137 or maintain a fork with your 
change in it.



---
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.
---

Reply via email to