You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by cruhland <gi...@git.apache.org> on 2016/12/07 02:01:54 UTC

[GitHub] curator pull request #176: [CURATOR-361] Prevent removal of leading slash fr...

GitHub user cruhland opened a pull request:

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

    [CURATOR-361] Prevent removal of leading slash from path when empty namespace used

    In the test, I'm casting `CuratorFramework` to `CuratorFrameworkImpl` to get access to `unfixForNamespace()`. It was the most direct way to write the test, but I'm open to suggestions for cleaner code.

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

    $ git pull https://github.com/cruhland/curator CURATOR-361

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

    https://github.com/apache/curator/pull/176.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 #176
    
----
commit 82a8906ddb185e4d405056aeed8abc807f440440
Author: Charles Ruhland <ch...@mesosphere.io>
Date:   2016-12-07T01:53:12Z

    [CURATOR-361] Prevent removal of leading slash from path when empty namespace used

----


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

[GitHub] curator pull request #176: [CURATOR-361] Prevent removal of leading slash fr...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


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