Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/1728#issuecomment-50972433
Yup, I think cherry picking is a good point. The changes are trivial but it
can be non-obvious later when picking apart why a merge conflict happens. Even
a little hassle may not be worth it.
I had hoped to be able to zap some of these cross-cutting improvements
right before a release as a good number are flagged in my IDE, but it may be at
a velocity now where that's not feasible and too late for that. In any event,
these can be reproduced automatically later if desired.
Yes definitely something to attack while editing nearby code anyway.
---
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]
