Thanks
On Feb 26, 2014 7:24 PM, "Patrick Wendell" wrote:
> You need to fork the new apache repository.
>
> 1. Fork https://github.com/apache/spark/ in github
> 2. Add your own fork as a remote in your local git
> ===> git remote add apache-pwendell g...@github.com:pwendell/spark.git
> 3. Push you
You need to fork the new apache repository.
1. Fork https://github.com/apache/spark/ in github
2. Add your own fork as a remote in your local git
===> git remote add apache-pwendell g...@github.com:pwendell/spark.git
3. Push your local branch the fork on github.
4. Make a pull request from your fo
github is not aware of the new repo being a "base-fork", so its not easy to
re-point pull requests. i am guessing it didnt get cloned from the
incubator spark one?
On Wed, Feb 26, 2014 at 5:56 PM, Patrick Wendell wrote:
> Sorry if this wasn't clear - If you are in the middle of a review
> close
Sorry if this wasn't clear - If you are in the middle of a review
close it and re-open it in against [1]. The reason is we can't test
your changes against incubator-spark because it no longer exists.
[1] https://github.com/apache/spark
- Patrick
On Wed, Feb 26, 2014 at 2:45 PM, Nan Zhu wrote:
>
Hi, Patrick,
How to deal with the active pull requests in the old repository?
The contributors have to do something?
Best,
--
Nan Zhu
On Wednesday, February 26, 2014 at 5:37 PM, Patrick Wendell wrote:
Hey All,
The github incubator-spark mirror has been migrated to [1] by Apache
infra and w
Hey All,
The github incubator-spark mirror has been migrated to [1] by Apache
infra and we've migrated Jenkins to reflect the new changes. This
means the existing "incubator-spark" mirror is becoming outdated and
no longer correctly displays pull request diff's.
We've asked apache infra to see if
