New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-2859] Update url of Kryo project in related docs #1782

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
5 participants
@gchen
Contributor

gchen commented Aug 5, 2014

JIRA Issue: https://issues.apache.org/jira/browse/SPARK-2859

Kryo project has been migrated from googlecode to github, hence we need to update its URL in related docs such as tuning.md.

@AmplabJenkins

This comment has been minimized.

Show comment
Hide comment
@AmplabJenkins

AmplabJenkins Aug 5, 2014

Can one of the admins verify this patch?

AmplabJenkins commented Aug 5, 2014

Can one of the admins verify this patch?

@gchen gchen changed the title from [SPARK-2859] update url of Kryo project in related docs to [SPARK-2859] Update url of Kryo project in related docs Aug 5, 2014

@rxin

This comment has been minimized.

Show comment
Hide comment
@rxin

rxin Aug 5, 2014

Contributor

Jenkins, test this please.

Contributor

rxin commented Aug 5, 2014

Jenkins, test this please.

@SparkQA

This comment has been minimized.

Show comment
Hide comment
@SparkQA

SparkQA Aug 5, 2014

QA tests have started for PR 1782. This patch merges cleanly.
View progress: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17936/consoleFull

SparkQA commented Aug 5, 2014

QA tests have started for PR 1782. This patch merges cleanly.
View progress: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17936/consoleFull

@SparkQA

This comment has been minimized.

Show comment
Hide comment
@SparkQA

SparkQA Aug 5, 2014

QA results for PR 1782:
- This patch PASSES unit tests.
- This patch merges cleanly
- This patch adds no public classes

For more information see test ouptut:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17936/consoleFull

SparkQA commented Aug 5, 2014

QA results for PR 1782:
- This patch PASSES unit tests.
- This patch merges cleanly
- This patch adds no public classes

For more information see test ouptut:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17936/consoleFull

@pwendell

This comment has been minimized.

Show comment
Hide comment
@pwendell

pwendell Aug 5, 2014

Contributor

Thanks - I merged this

Contributor

pwendell commented Aug 5, 2014

Thanks - I merged this

asfgit pushed a commit that referenced this pull request Aug 5, 2014

[SPARK-2859] Update url of Kryo project in related docs
JIRA Issue: https://issues.apache.org/jira/browse/SPARK-2859

Kryo project has been migrated from googlecode to github, hence we need to update its URL in related docs such as tuning.md.

Author: Guancheng (G.C.) Chen <chenguancheng@gmail.com>

Closes #1782 from gchen/kryo-docs and squashes the following commits:

b62543c [Guancheng (G.C.) Chen] update url of Kryo project
(cherry picked from commit ac3440f)

Signed-off-by: Patrick Wendell <pwendell@gmail.com>

@asfgit asfgit closed this in ac3440f Aug 5, 2014

asfgit pushed a commit that referenced this pull request Aug 5, 2014

[SPARK-2859] Update url of Kryo project in related docs
JIRA Issue: https://issues.apache.org/jira/browse/SPARK-2859

Kryo project has been migrated from googlecode to github, hence we need to update its URL in related docs such as tuning.md.

Author: Guancheng (G.C.) Chen <chenguancheng@gmail.com>

Closes #1782 from gchen/kryo-docs and squashes the following commits:

b62543c [Guancheng (G.C.) Chen] update url of Kryo project
(cherry picked from commit ac3440f)

Signed-off-by: Patrick Wendell <pwendell@gmail.com>

@gchen gchen deleted the gchen:kryo-docs branch Aug 6, 2014

@gchen gchen restored the gchen:kryo-docs branch Aug 6, 2014

xiliu82 pushed a commit to xiliu82/spark that referenced this pull request Sep 4, 2014

[SPARK-2859] Update url of Kryo project in related docs
JIRA Issue: https://issues.apache.org/jira/browse/SPARK-2859

Kryo project has been migrated from googlecode to github, hence we need to update its URL in related docs such as tuning.md.

Author: Guancheng (G.C.) Chen <chenguancheng@gmail.com>

Closes #1782 from gchen/kryo-docs and squashes the following commits:

b62543c [Guancheng (G.C.) Chen] update url of Kryo project

CodingCat pushed a commit to CodingCat/spark that referenced this pull request Sep 6, 2014

[SPARK-2859] Update url of Kryo project in related docs
JIRA Issue: https://issues.apache.org/jira/browse/SPARK-2859

Kryo project has been migrated from googlecode to github, hence we need to update its URL in related docs such as tuning.md.

Author: Guancheng (G.C.) Chen <chenguancheng@gmail.com>

Closes #1782 from gchen/kryo-docs and squashes the following commits:

b62543c [Guancheng (G.C.) Chen] update url of Kryo project

danosipov added a commit to danosipov/spark that referenced this pull request Sep 8, 2014

[SPARK-2859] Update url of Kryo project in related docs
JIRA Issue: https://issues.apache.org/jira/browse/SPARK-2859

Kryo project has been migrated from googlecode to github, hence we need to update its URL in related docs such as tuning.md.

Author: Guancheng (G.C.) Chen <chenguancheng@gmail.com>

Closes #1782 from gchen/kryo-docs and squashes the following commits:

b62543c [Guancheng (G.C.) Chen] update url of Kryo project

dgshep pushed a commit to dgshep/spark that referenced this pull request Dec 8, 2014

[SPARK-2859] Update url of Kryo project in related docs
JIRA Issue: https://issues.apache.org/jira/browse/SPARK-2859

Kryo project has been migrated from googlecode to github, hence we need to update its URL in related docs such as tuning.md.

Author: Guancheng (G.C.) Chen <chenguancheng@gmail.com>

Closes #1782 from gchen/kryo-docs and squashes the following commits:

b62543c [Guancheng (G.C.) Chen] update url of Kryo project

@gchen gchen deleted the gchen:kryo-docs branch Feb 27, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment