Github user blerer commented on the issue:
https://github.com/apache/cassandra/pull/85
Thanks. :-)
People are usually tracking the JIRA tickets and not the pull requests. So
it is best to keep it in sync with your developments.
---
If your project is set up for it, you can reply
Github user iksaif commented on the issue:
https://github.com/apache/cassandra/pull/85
Done, I'm not yet very familiar with the workflow.
---
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
Github user blerer commented on the issue:
https://github.com/apache/cassandra/pull/85
I guess it is CASSANDRA-12915. Could you mark it as patch available?
---
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 d
Github user blerer commented on the issue:
https://github.com/apache/cassandra/pull/85
Is there a JIRA ticket associated to your patch?
---
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 fe