Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/9571
> I was secretly hoping you'd just give up on this patch, since it will
generate a lot of conflicts with the code I'm working on in parallel..
No. Sorry
I do suspect the reviewers of my other outstanding patches are of the same
mind "if we ignore him, he'll go away". which is why I'm effectively giving up
filing new patches and bug reports related to Spark.
However, that doesn't mean that I'm going to stop updating and reminding
people of my current set of patches. It's easier to accept them and hope I'll
go away afterwards. After all, if you'd merged this in earlier: no merge
conflicts. Better all round.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
