Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Received-SPF: pass (nike.apache.org: domain of mckenzie.cam@gmail.com
 designates 209.85.217.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20141119063543.ABA4B9AA6D0@tyr.zones.apache.org>
References: <git-pr-55-curator@git.apache.org>
	<20141119063543.ABA4B9AA6D0@tyr.zones.apache.org>
Date: Wed, 19 Nov 2014 17:38:31 +1100
Message-ID: 
 <CANykduaA2r8OkHfRB_bh60gty8+Rs2XKo+sUzNUnqJBKj0ZZZA@mail.gmail.com>
Subject: Re: [GitHub] curator pull request: CURATOR-167 - Partial fix to clean
 up Curato...
From: Cameron McKenzie <mckenzie.cam@gmail.com>
To: dev@curator.apache.org
Content-Type: multipart/alternative; boundary=001a11c38506d41b7505083075f8

--001a11c38506d41b7505083075f8
Content-Type: text/plain; charset=UTF-8

I don't think path children cache does, I think that tree cache may, will
have a look tomorrow
On Nov 19, 2014 5:35 PM, "dragonsinth" <git@git.apache.org> wrote:

> Github user dragonsinth commented on the pull request:
>
>     https://github.com/apache/curator/pull/55#issuecomment-63598493
>
>     BTW: do PathChildrenCache and TreeCache have similar issues?
>
>
> ---
> 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.
> ---
>

--001a11c38506d41b7505083075f8--