curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cammckenzie <...@git.apache.org>
Subject [GitHub] curator pull request: Curator 110
Date Mon, 02 Jun 2014 23:03:16 GMT
GitHub user cammckenzie opened a pull request:

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

    Curator 110

    Fix for CURATOR-110

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

    $ git pull https://github.com/cammckenzie/curator CURATOR-110

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

    https://github.com/apache/curator/pull/9.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 #9
    
----
commit 1a63a102ebbaaead265babd71a3d52928f848bd0
Author: Cameron McKenzie <cameron@unico.com.au>
Date:   2014-06-02T06:30:26Z

    CURATOR-110 - Modified state handling to treat 'CONNECTED' and
    'RECONNECTED' events in the same way. Added a test case for the leader
    latch being started before a connection to ZK has been established.

commit 0b7ae7e3672a9c817fe31144cd6b18d9a357f124
Author: Cameron McKenzie <cameron@unico.com.au>
Date:   2014-06-02T23:01:31Z

    CURATOR-110 - Fixed up formatting to Curator standards

----


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