Github user blerer commented on the issue:
https://github.com/apache/cassandra/pull/98
@MikkelTAndersen Could you also add some unit tests 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
Github user blerer commented on the issue:
https://github.com/apache/cassandra/pull/86
I guess that you did not really intend to create that pull request.
---
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
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 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
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
Github user blerer commented on the pull request:
https://github.com/apache/cassandra/pull/62#issuecomment-174888193
Hi,
This repository is just a mirror and does not accept pull requests.
Could you open a JIRA ticket and attach your patch to it?
Thanks
Github user blerer commented on the pull request:
https://github.com/apache/cassandra/pull/58#issuecomment-165125795
We cannot merge the PR because this repository is only a mirror from:
git://git.apache.org/cassandra.git
I have committed your patch. Could you close your pull
