Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-155142564
Merging into master 1.6
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-155142100
Hi sorry I've been out for vacation I will have a look at this now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9538
---
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
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-155122108
Ping @andrewor14
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-154808245
@andrewor14 does that seem OK to you? Looks like the PR went only to master
so this needs to go to master?
---
If your project is set up for it, you can reply to this
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-154988152
Knock, knock. Can we do someting with the patch as the build procedure for
Scala 2.11 expanded with another step - `git merge pr-9538` beside
