Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/5423#issuecomment-117249952
> though everyone has to recognise that the two patches need to be fully
consistent to work.
That's fine. You can mention that the patch depends on a previous one, for
example, or include the previous patch on the later one and ask people to just
look at particular commits (at least until the first one checks in). It's just
that reviewing a big patch is a lot of work, especially if you're not the
person who wrote the code. Breaking it down will most certainly make the review
cycle go faster.
---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
