curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From brienwheeler-sqrrl <...@git.apache.org>
Subject [GitHub] curator pull request: CURATOR-140: Allow InterProcessReadWriteLock...
Date Fri, 24 Oct 2014 16:34:59 GMT
GitHub user brienwheeler-sqrrl opened a pull request:

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

    CURATOR-140: Allow InterProcessReadWriteLock consumer to set lock node d...

    Simple change to plumb through the ability to set node data from the consumer of InterProcessReadWriteLock.

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

    $ git pull https://github.com/sqrrldata/curator CURATOR-140

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

    https://github.com/apache/curator/pull/48.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 #48
    
----
commit 77a1afbcc074d9ef87ba3bfc7d3cb641ad2f727e
Author: Brien Wheeler <brien@briens-macbook-pro.local>
Date:   2014-10-24T16:33:16Z

    CURATOR-140: Allow InterProcessReadWriteLock consumer to set lock node data.

----


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