[GitHub] spark pull request: Updated more links in documentation

Github user jyotiska closed the pull request at: https://github.com/apache/spark/pull/23 --- 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 enab

[GitHub] spark pull request: Updated more links in documentation

Github user rxin commented on the pull request: https://github.com/apache/spark/pull/23#issuecomment-36449072 #2 was actually merged. @jyotiska do you mind closing 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

[GitHub] spark pull request: Updated more links in documentation

Github user jyotiska commented on the pull request: https://github.com/apache/spark/pull/23#issuecomment-36216611 Right, didn't notice that PR. --- 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] spark pull request: Updated more links in documentation

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/23#issuecomment-36216059 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] spark pull request: Updated more links in documentation

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/23#issuecomment-36216060 All automated tests passed. Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12906/ --- If your project i

[GitHub] spark pull request: Updated more links in documentation

Github user pwendell commented on the pull request: https://github.com/apache/spark/pull/23#issuecomment-36215928 I think this is redundant with #2 --- 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

[GitHub] spark pull request: Updated more links in documentation

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/23#issuecomment-36214553 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] spark pull request: Updated more links in documentation

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/23#issuecomment-36214523 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] spark pull request: Updated more links in documentation

Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/23#issuecomment-36214522 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] spark pull request: Updated more links in documentation

GitHub user jyotiska opened a pull request: https://github.com/apache/spark/pull/23 Updated more links in documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/jyotiska/spark pyspark_docs2 Alternatively you can review an