ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dkarachentsev <...@git.apache.org>
Subject [GitHub] ignite pull request: Ignite 2430
Date Thu, 11 Feb 2016 16:15:36 GMT
GitHub user dkarachentsev opened a pull request:


    Ignite 2430


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

    $ git pull https://github.com/dkarachentsev/ignite ignite-2430

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 #475
commit 946dccb9e98419bf9921b12607667d74ef87ecda
Author: dkarachentsev <dkarachentsev@gridgain.com>
Date:   2016-02-10T08:33:04Z

    IGNITE-2575 Add limit on minimal value of IGFS IPC port configuration.

commit 3d5999821d0efd6c026adbb3256c86bc798dc1c7
Author: dkarachentsev <dkarachentsev@gridgain.com>
Date:   2016-02-10T08:50:09Z

    Merge remote-tracking branch 'upstream/master'

commit 375eb11ba8c9076906971785fdb7bead294d8022
Author: dkarachentsev <dkarachentsev@gridgain.com>
Date:   2016-02-11T09:47:18Z

    Merge remote-tracking branch 'upstream/master'

commit 9cbee07c3a44de71dc25aa0ef23f620c12a0ecc4
Author: dkarachentsev <dkarachentsev@gridgain.com>
Date:   2016-02-11T16:12:18Z

    GNITE-2430 - Fix BinaryObject: Inconsistent field type name is returned for Collections


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