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 <pwend...@gmail.com> wrote:

> 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 <zhunanmcg...@gmail.com> 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 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 they can migrate existing pull
> > requests to incubator-spark. However since this relies on coordinating
> > with github, I'm not entirely sure whether they can do this or what
> > the timeline would be.
> >
> > In the mean time it would be good for people to open new pull requests
> > against [1]. For pull requests that were *just* about to be merged, we
> > can go manually merge them, but ones that require feedback and more
> > rounds of testing will need to be done on the new one since
> > incubator-spark is now out of date.
> >
> > Sorry about this inconvenience, it is a one-time transition and we
> > won't ever have to do it again.
> >
> > [1] https://github.com/apache/spark
> >
> > - Patrick
>

Reply via email to