[GitHub] ignite pull request: TESTING BRANCH, DO NOT MERGE Ignite 2343 temp...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request: TESTING BRANCH, DO NOT MERGE Ignite 2343 temp...

andrey-kuznetsov
GitHub user iveselovskiy opened a pull request:

    https://github.com/apache/ignite/pull/401

    TESTING BRANCH, DO NOT MERGE Ignite 2343 temp do not merge

   

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

    $ git pull https://github.com/iveselovskiy/ignite ignite-2343-temp-do-not-merge

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

    https://github.com/apache/ignite/pull/401.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 #401
   
----
commit 9a8ba90abc9737c0e0ea7e3dc2aa5ce240f66d5b
Author: iveselovskiy <[hidden email]>
Date:   2016-01-12T16:22:31Z

    IGNITE-2343: workable fix for the customer issue.

commit 24e9ad293530a42a85a17e20352306bd1f5a81c1
Author: iveselovskiy <[hidden email]>
Date:   2016-01-13T15:26:55Z

    Special branch with Snappy tests only in Hadoop tests suite. For testing purposes only, do not merge.

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #401: TESTING BRANCH, DO NOT MERGE Ignite 2343 temp do n...

andrey-kuznetsov
Github user iveselovskiy closed the pull request at:

    https://github.com/apache/ignite/pull/401


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---