ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ilantukh <...@git.apache.org>
Subject [GitHub] ignite pull request: IGNITE-2700
Date Fri, 26 Feb 2016 15:06:58 GMT
GitHub user ilantukh opened a pull request:




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

    $ git pull https://github.com/gridgain/apache-ignite ignite-2700

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


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

    This closes #518
commit 2fc88c57ebad5ea2ab5bd70f8fe7d34b900a0080
Author: Ilya Lantukh <ilantukh@gridgain.com>
Date:   2016-02-20T11:46:53Z

    New versions of closures.

commit 1758a59be5c2c08f67b7a12508c118e5d9a95225
Author: Ilya Lantukh <ilantukh@gridgain.com>
Date:   2016-02-20T13:12:03Z

    ignite-2700 : Version selection logic.

commit be12521cfc98b237fa2db47973234294b539d1e3
Author: Ilya Lantukh <ilantukh@gridgain.com>
Date:   2016-02-25T12:24:38Z

    ignite-2700 : Fixed problems found during code review.

commit 9af0aa5de957c625104f2becffce57105c69eda8
Author: Ilya Lantukh <ilantukh@gridgain.com>
Date:   2016-02-26T14:51:08Z

    ignite-2700 : Closure compatibility optimizations.


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.

View raw message