GitHub user peterpi0915 opened a pull request:

    https://github.com/apache/spark/pull/17971

    Branch 0.5

    ## What changes were proposed in this pull request?
    
    (Please fill in changes proposed in this fix)
    
    ## How was this patch tested?
    
    (Please explain how this patch was tested. E.g. unit tests, integration 
tests, manual tests)
    (If this patch involves UI changes, please attach a screenshot; otherwise, 
remove this)
    
    Please review http://spark.apache.org/contributing.html before opening a 
pull request.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/spark branch-0.5

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/17971.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #17971
    
----
commit 1b9bba0e9aea82c0390d4c43098c08940d3b0309
Author: Thomas Dudziak <[email protected]>
Date:   2012-10-09T22:21:38Z

    Support for Hadoop 2 distributions such as cdh4
    
    Conflicts:
    
        core/src/main/scala/spark/NewHadoopRDD.scala
        core/src/main/scala/spark/PairRDDFunctions.scala
        project/SparkBuild.scala

commit 8eec96fa5436902d2aa24cf8700b4424aff2005a
Author: Matei Zaharia <[email protected]>
Date:   2012-11-21T02:23:34Z

    Change version to 0.5.2

commit 5b021ce0990ec675afc6939cc2c06f041c973d17
Author: Matei Zaharia <[email protected]>
Date:   2012-11-23T00:26:15Z

    Change version to 0.5.3-SNAPSHOT

----


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