This is an automated email from the ASF dual-hosted git repository.
andor pushed a change to branch branch-3.4
in repository https://gitbox.apache.org/repos/asf/zookeeper.git.
discard 5207f27 ZOOKEEPER-3262: Update dependencies flagged by OWASP report
discard c1a58d7 ZOOKEEPER-3122: Bugfix - Change maven java target versions to
1.6
discard b64dae3 Prepare for the next release: update the version to
3.4.15-SNAPSHOT
new 3788d76 ZOOKEEPER-3122: Bugfix - Change maven java target versions to
1.6
new 927d0e4 ZOOKEEPER-3262: Update dependencies flagged by OWASP report
new 9f1735b Prepare for the next release: update the version to
3.4.15-SNAPSHOT
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 (5207f27)
\
N -- N -- N refs/heads/branch-3.4 (9f1735b)
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:
