You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by nchammas <gi...@git.apache.org> on 2014/08/03 09:08:02 UTC

[GitHub] spark pull request: [SPARK-2627] [PySpark] have the build enforce ...

Github user nchammas commented on the pull request:

    https://github.com/apache/spark/pull/1744#issuecomment-50983745
  
    Hey Pat!
    
    1. I've edited the title accordingly.
    2. Makes sense. I'll take a crack at fetching `pep8` lazily as you describe. Is there something you can point me to that I can use as a reference for how to do this?
    
    By the way, I'm not sure I resolved my merge conflicts in the best way. It looks like changes I merged into my fork from upstream got re-included in this PR.
    
    Is there a quick way to fix this? Apologies, I'm still learning how to use git properly.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org