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 771b744 CURATOR-549
discard 72d4df6 CURATOR-549
discard 1ff910c CURATOR-549
add 0d8c55a CURATOR-549
new 81b31c5 CURATOR-549
new 2109a03 CURATOR-549
new 2ab880f x
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 (771b744)
\
N -- N -- N
refs/heads/CURATOR-549-zk36-persistent-watcher-bridge (2ab880f)
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 3 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:
.../cache/CuratorCacheBridgeBuilderImpl.java | 2 +-
.../framework/recipes/cache/CuratorCacheImpl.java | 35 ++-----------
.../framework/recipes/cache/OutstandingOps.java | 60 ++++++++++++++++++++++
3 files changed, 66 insertions(+), 31 deletions(-)
create mode 100644
curator-recipes/src/main/java/org/apache/curator/framework/recipes/cache/OutstandingOps.java
