This is an automated email from the ASF dual-hosted git repository.
kezhuw pushed a change to branch
CURATOR-728-ZkPaths-mkdirs-not-issue-create-if-possible
in repository https://gitbox.apache.org/repos/asf/curator.git
omit 0fb6f3a07 CURATOR-728: Not issue ZooKeeper::create if possible in
ZkPaths::mkdirs
add ba387f2b3 CURATOR-728: Not issue ZooKeeper::create if possible in
ZkPaths::mkdirs
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 (0fb6f3a07)
\
N -- N -- N
refs/heads/CURATOR-728-ZkPaths-mkdirs-not-issue-create-if-possible (ba387f2b3)
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.
No new revisions were added by this update.
Summary of changes:
.../src/test/java/org/apache/curator/framework/imps/TestCreate.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
