Github user florianverhein commented on the pull request:

    https://github.com/apache/spark/pull/4385#issuecomment-73443768
  
    @nchammas I can revert the input check back to what I had earlier to 
enforce `spark-ec2` only. We can remove the check later if needed. 
    Given the help string and the type of user who would try forks with 
different names, I think it's over-cautious. But I'm more concerned with 
getting this finalised so really have no strong opinions. You can decide ;-)
    
    Apart from this (please let me know what you'd like) and the "github" input 
check you mentioned above, is there anything else required? We've done a full 
circle and the testing loop is expensive (time to spin up EC2 clusters and 
manually check, etc), so I'd really like to get this PR out of the way.


---
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]

Reply via email to