[GitHub] ignite pull request #1968: Ignite 4575 binary enum for test purposes

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

[GitHub] ignite pull request #1968: Ignite 4575 binary enum for test purposes

andrey-kuznetsov
GitHub user skalashnikov opened a pull request:

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

    Ignite 4575 binary enum for test purposes

   

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

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

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

    https://github.com/apache/ignite/pull/1968.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 #1968
   
----
commit 237d3a2dcd9df2da6f28468e721da5a15b05bd1c
Author: skalashnikov <[hidden email]>
Date:   2017-05-04T10:20:46Z

    IGNITE-4575: isolated changes for binary enum

commit fb10ce1602aceb435a03905a9f9e812148f00839
Author: devozerov <[hidden email]>
Date:   2017-05-05T09:01:04Z

    Merge branch 'master' into ignite-4575-binary

commit b13fd8d66da3e49f1354118631c0d14d92f2a309
Author: devozerov <[hidden email]>
Date:   2017-05-05T09:11:42Z

    Public API review.

commit aa153c4d40f06b6c073e90d2d49ae1d51b0f35d9
Author: devozerov <[hidden email]>
Date:   2017-05-05T10:13:37Z

    Merge branch 'master' into ignite-4575-binary

commit e4f11ab9e1997ec63328d93a2714691b1104560e
Author: devozerov <[hidden email]>
Date:   2017-05-05T10:53:36Z

    Minors.

commit ffc4217194570bfbe3e7c7a459dd084325550c42
Author: skalashnikov <[hidden email]>
Date:   2017-05-05T19:55:49Z

    IGNITE-4575: applied review comments

commit e280cd1004443656dd29c80f6b9381eebc6ddf89
Author: skalashnikov <[hidden email]>
Date:   2017-05-10T12:38:53Z

    IGNITE-4575: review comments

commit ff0202702b84f4b95a6053d5b59671dbd6762694
Author: skalashnikov <[hidden email]>
Date:   2017-05-10T13:15:09Z

    IGNITE-4575: review comments

commit 197bf0ac191d0032d9a33bfe2cb772f359245e1a
Author: skalashnikov <[hidden email]>
Date:   2017-05-10T15:35:13Z

    IGNITE-4575: review comments

commit fe391fcc344f8110803d93582ea705d172c2d4fe
Author: skalashnikov <[hidden email]>
Date:   2017-05-10T16:13:07Z

    IGNITE-4575: fixed tests

commit 3cf25afe9bbae27e3b2027f422aaa7997396b877
Author: skalashnikov <[hidden email]>
Date:   2017-05-10T16:21:16Z

    Merge branch 'master' of https://github.com/apache/ignite into ignite-4575-binary

commit 3c92d4e8047fac16de3b9dc38fcc5936ea3b1460
Author: devozerov <[hidden email]>
Date:   2017-05-16T11:08:38Z

    Merge branch 'master' into ignite-4575-binary

commit 270a56d663f89d4c082c1f105b77029008757493
Author: devozerov <[hidden email]>
Date:   2017-05-16T13:35:07Z

    Minors.

commit 16bb32590af0f478673e5e7b7141b0947eba8cb7
Author: skalashnikov <[hidden email]>
Date:   2017-05-17T16:25:52Z

    IGNITE-4509: applied review comments

commit 89c6ed67f22c24861df0d9eebf1a7bae75890350
Author: skalashnikov <[hidden email]>
Date:   2017-05-18T10:46:28Z

    IGNITE-4575: applied review comments

commit 3de400aee352e9ce0d0d81f744785b88d02a2224
Author: skalashnikov <[hidden email]>
Date:   2017-05-18T10:47:42Z

    Merge branch 'master' of https://github.com/apache/ignite into ignite-4575-binary

----


---
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 #1968: Ignite 4575 binary enum for test purposes

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

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


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