ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ezhuravl <...@git.apache.org>
Subject [GitHub] ignite pull request #1578: Ignite 3386
Date Mon, 27 Feb 2017 14:34:50 GMT
GitHub user ezhuravl opened a pull request:

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

    Ignite 3386

    

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

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

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

    https://github.com/apache/ignite/pull/1578.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 #1578
    
----
commit 1ef4bf43af6d82af36e5f7dd3b4ad33bc94eb9aa
Author: Evgenii Zhuravlev <ezhuravlev@gridgain.com>
Date:   2017-02-27T14:32:12Z

    IGNITE-3386 Re-create lock state if lock owner leaves topology

commit fba0b733318c71b8560dc4d18260a858e88a6ea1
Author: Evgenii Zhuravlev <ezhuravlev@gridgain.com>
Date:   2017-02-27T14:33:40Z

    IGNITE-3386 Re-create lock state if lock owner leaves topology

----


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

Mime
View raw message