This is an automated email from the ASF dual-hosted git repository.
randgalt pushed a change to branch CURATOR-549-zk36-persistent-watcher-bridge
in repository https://gitbox.apache.org/repos/asf/curator.git.
discard 38c69ae Added a bridge facade so that ServiceCache and ModeledCache
can use CuratorCache when running in ZK 3.6 and fall back to TreeCache for
older ZK libs
discard 4771b72 Add recipes that use persistent watchers including new cache
recipes to replace all others.
discard 931ec04 Support persistent watchers in ZK 3.6+ while maintaining
background compatability with previous versions of ZK. Added a new module to
make sure we maintain comaptibility with ZK 3.5.x
add a8ba00d CURATOR-549
add 40478c5 CURATOR-549
add f1d6989 Add recipes that use persistent watchers including new cache
recipes to replace all others.
new 37763fc CURATOR-549
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 (38c69ae)
\
N -- N -- N
refs/heads/CURATOR-549-zk36-persistent-watcher-bridge (37763fc)
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:
