ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From daradurvs <...@git.apache.org>
Subject [GitHub] ignite pull request #2236: test-PR-ignite-5097
Date Tue, 04 Jul 2017 16:14:08 GMT
GitHub user daradurvs opened a pull request:




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

    $ git pull https://github.com/Sberbank-Technology/ignite ignite-5097

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 #2236
commit 1e1e8432dc936df7c62557575a57c4a159b4bca6
Author: Vyacheslav Daradur <daradurvs@gmail.com>
Date:   2017-05-31T08:41:56Z

    ignite-5097: writing arrays length in varint encoding was implemented

commit d162d3e3d9036cddb275b4a3d86b8f5de9795185
Author: daradurvs <daradurvs@gmail.com>
Date:   2017-06-01T18:35:13Z

    ignite-5097: doUnsafeWriteUnsignedVarint method was added

commit bfe381b3a7498eb5bebeb25026a43d36656c6041
Author: daradurvs <daradurvs@gmail.com>
Date:   2017-06-04T21:25:48Z

    ignite-5097: dotNET - writing arrays length in varint encoding was implemented

commit 516fcf41e4e973abf41cdd19acd2c9ea1bfb9445
Author: daradurvs <daradurvs@gmail.com>
Date:   2017-06-04T21:26:00Z

    ignite-5097: dotNET - hardcoded hashcode values in the tests were changed according to
new conditions


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