This is an automated email from the ASF dual-hosted git repository.
eolivelli pushed a change to branch branch-2.9
in repository https://gitbox.apache.org/repos/asf/pulsar.git.
discard af5ce3f Fixing permissions of scripts used to deploy docker images
(#11951)
discard 6366405 [ML] Add OpAddEntry to pendingAddEntries after the state
check (#12570)
discard 393f95c [Transaction] Fix transaction system topic create in loop.
(#12749)
new bce5d56 [ML] Add OpAddEntry to pendingAddEntries after the state
check (#12570)
new 7d1bc57 Fixing permissions of scripts used to deploy docker images
(#11951)
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 (af5ce3f)
\
N -- N -- N refs/heads/branch-2.9 (7d1bc57)
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 2 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:
.../pulsar/broker/transaction/TransactionTest.java | 57 ----------------------
1 file changed, 57 deletions(-)