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 #2026: IGNITE-5299 Don't set IgniteLock as broken if loc...
Date Mon, 29 May 2017 14:02:42 GMT
GitHub user ezhuravl opened a pull request:

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

    IGNITE-5299 Don't set IgniteLock as broken if lock is failoverSafe

    

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

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

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

    https://github.com/apache/ignite/pull/2026.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 #2026
    
----
commit 02ebe624a37379055345ae1409918ba96da1d3fc
Author: Evgenii Zhuravlev <ezhuravlev@gridgain.com>
Date:   2017-05-29T13:46:11Z

    IGNITE-5299 Don't set IgniteLock as broken if lock is failoverSafe

----


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