This is an automated email from the ASF dual-hosted git repository.

randgalt pushed a change to branch CURATOR-623
in repository https://gitbox.apache.org/repos/asf/curator.git.


 discard 5c90640  `ChildrenCache` (used by Queues) didn't have a 
`ConnectionStateListener`. Thus, if a long network partition occurred the ZK 
instance would be recreated losing any set watcher and the ChildrenCache would 
fail to continue watching changes. Adding a ConnectionStateListener fixes this.
     new ad5b164  `ChildrenCache` (used by Queues) didn't have a 
`ConnectionStateListener`. Thus, if a long network partition occurred the ZK 
instance would be recreated losing any set watcher and the ChildrenCache would 
fail to continue watching changes. Adding a ConnectionStateListener fixes this.

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (5c90640)
            \
             N -- N -- N   refs/heads/CURATOR-623 (ad5b164)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:

Reply via email to