Skip to content

Conversation

@vinodkc
Copy link
Contributor

@vinodkc vinodkc commented Mar 21, 2015

No description provided.

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@mengxr
Copy link
Contributor

mengxr commented Mar 21, 2015

ok to test

@mengxr
Copy link
Contributor

mengxr commented Mar 21, 2015

LGTM pending Jenkins

@SparkQA
Copy link

SparkQA commented Mar 21, 2015

Test build #28943 has started for PR 5112 at commit 2c6aee6.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Mar 21, 2015

Test build #28943 has finished for PR 5112 at commit 2c6aee6.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28943/
Test PASSed.

@srowen
Copy link
Member

srowen commented Mar 22, 2015

LGTM - @jkbradley I suppose we can merge this and ... keep SPARK-6337 open or is it worth just making a new JIRA should any other doc issues come up? (or just a follow-on PR?) meaning, can we resolve it once this is merged?

@jkbradley
Copy link
Member

Resolving the JIRA sounds fine to me.

vinodkc added a commit that referenced this pull request Mar 22, 2015
Author: vinodkc <[email protected]>

Closes #5112 from vinodkc/spark_1.3_doc_fixes and squashes the following commits:

2c6aee6 [vinodkc] Spark 1.3 doc fixes

(cherry picked from commit 2bf40c5)
Signed-off-by: Sean Owen <[email protected]>
@asfgit asfgit closed this in 2bf40c5 Mar 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants