Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
From: madrob <git@git.apache.org>
To: dev@curator.apache.org
Reply-To: dev@curator.apache.org
Message-ID: <git-pr-39-curator@git.apache.org>
Subject: [GitHub] curator pull request: CURATOR-136 Make LeaderLatch handling
 of rel...
Content-Type: text/plain
Date: Wed, 20 Aug 2014 14:16:24 +0000 (UTC)

GitHub user madrob opened a pull request:

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

    CURATOR-136 Make LeaderLatch handling of relative paths consistent.

    LeaderLatch would previously normalize a relative path in some places
    but not others, causing inconsistent behavior. Make it check for an
    absolute path on startup.

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

    $ git pull https://github.com/madrob/curator CURATOR-136

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

    https://github.com/apache/curator/pull/39.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 #39
    
----
commit 0f598860e78dd4796eb8af8cfcc370952258bded
Author: Mike Drob <mdrob@cloudera.com>
Date:   2014-08-11T20:12:53Z

    CURATOR-136 Make LeaderLatch handling of relative paths consistent.
    
    LeaderLatch would previously normalize a relative path in some places
    but not others, causing inconsistent behavior. Make it check for an
    absolute path on startup.

----


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