Github user erikerlandson commented on the issue:
https://github.com/apache/spark/pull/16061
@iyanuobidele the current head of this branch should be equivalent, but it
can't hurt to rebase just in case.
@foxish yesterday occurred to me that it would've been sensible set up a GH
organization for this little consortium, and run the PR from there. Presumably
we still could. The drawback to making any change to it now is losing the
dialog that's happened here already.
The problem I'm interested in solving even more is ensuring that everybody
who contributes to this PR gets logged somehow in the upstream commit history
when this PR eventually gets merged. I don't think that would happen in the
case of a typical squash-merge, although I assume it _would_ using a rebase
merge. @rxin do you have any thoughts on that?
---
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
