Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/41
---
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 enable
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36449397
Thanks. I've merged this!
---
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 f
Github user ngbinh commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36449390
Yep, found the problem now. Should be fixed!
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36449234
Sorry @ngbinh you misunderstood me. I think the problem is the git commit
metadata doesn't actually contain the author information. It could be that the
email or the author in
Github user ngbinh commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36449199
just add Author to both PR and the commit.
---
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 do
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36449064
Actually I'm having trouble merging this. I think it's because your git
commit doesn't actually have any author information. Do you mind fixing that?
cc @pwendell here
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36449019
Thanks. I've merged this.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36308968
Merged build finished.
---
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36308969
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12923/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36306883
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36306872
Merged build started.
---
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36306871
Merged build triggered.
---
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 ngbinh opened a pull request:
https://github.com/apache/spark/pull/41
Update io.netty from 4.0.13 Final to 4.0.17.Final
This update contains a lot of bug fixes and some new perf improvements.
It is also binary compatible with the current 4.0.13.Final
For more
13 matches
Mail list logo