[GitHub] ignite pull request: IGNITE-1642 .Net: Rename EventType members

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

[GitHub] ignite pull request: IGNITE-1642 .Net: Rename EventType members

andrey-kuznetsov
GitHub user ptupitsyn opened a pull request:

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

    IGNITE-1642 .Net: Rename EventType members

   

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

    $ git pull https://github.com/ptupitsyn/ignite ignite-1642

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

    https://github.com/apache/ignite/pull/147.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 #147
   
----
commit 92790c9a512ecf3eaa6c75d50a5038ac8283f3d2
Author: ptupitsyn <[hidden email]>
Date:   2015-10-13T10:00:12Z

    Rename single events

commit 909df596465615b72e41493bd19c247934bca644
Author: ptupitsyn <[hidden email]>
Date:   2015-10-13T10:03:09Z

    wip

commit ce1393235e9a10268fafda90388ceb073e124fbe
Author: ptupitsyn <[hidden email]>
Date:   2015-10-13T10:03:52Z

    Remove FxCop suppressions

commit d35c69a3129bcdd36d52272465bb73870e3f4865
Author: ptupitsyn <[hidden email]>
Date:   2015-10-13T10:10:29Z

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

[GitHub] ignite pull request: IGNITE-1642 .Net: Rename EventType members

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

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


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