GitHub user nchammas opened a pull request:

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

    [Spark QA] [WIP] Include commit hash in Spark QA messages

    There is currently no JIRA issue for this PR, but you can find the 
[motivating discussion 
here](http://mail-archives.apache.org/mod_mbox/spark-dev/201408.mbox/%3CCABPQxssy0ri2QAz=cc9tx+exywarm7pncvm8apqcwc-eslb...@mail.gmail.com%3E).
 This is a work in progress.
    
    The goal of this PR (and related ones to come) is to include useful detail 
in Spark QA's messages that are intended to make a committer's job easier to do.
    
    Since this work depends on Jenkins, I cannot test this locally. Hence, I 
will be iterating via this PR.
    
    [Note: This is a duplicate of a [previous 
PR](https://github.com/apache/spark/pull/1811), without the extraneous commits.]

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

    $ git pull https://github.com/nchammas/spark master

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

    https://github.com/apache/spark/pull/1816.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 #1816
    
----
commit 8f641acec483de061ebe35f0712e05d6f1873975
Author: nchammas <[email protected]>
Date:   2014-08-06T22:25:18Z

    Merge pull request #7 from apache/master
    
    merge upstream changes

commit 0f3ee1c37c7d7b3d275e29ed679fd7cc4bf4f0b4
Author: Nicholas Chammas <[email protected]>
Date:   2014-08-06T22:27:20Z

    [Experimental] Include commit hash in QA message

----


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