Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
From: markap14 <git@git.apache.org>
To: dev@curator.apache.org
Reply-To: dev@curator.apache.org
Message-ID: <git-pr-158-curator@git.apache.org>
Subject: [GitHub] curator pull request #158: CURATOR-337: Do not attempt to release a mutex un...
Content-Type: text/plain
Date: Thu, 28 Jul 2016 00:21:28 +0000 (UTC)
archived-at: Thu, 28 Jul 2016 00:21:30 -0000

GitHub user markap14 opened a pull request:

    https://github.com/apache/curator/pull/158

    CURATOR-337: Do not attempt to release a mutex unless it has actually been acquired

    \Do not attempt to release a mutex unless it has actually been acquired

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

    $ git pull https://github.com/markap14/curator master

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

    https://github.com/apache/curator/pull/158.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 #158
    
----
commit fe19a8c9c5523a08cab1a0e16ec536e35c0a65b7
Author: Mark Payne <markap14@hotmail.com>
Date:   2016-07-28T00:17:40Z

    CURATOR-337: Do not attempt to release a mutex unless it has actually been acquired

----


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