This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 5b4da92d917 Regen for commit 96aa85ccfb119cd77d0f3edae9d273bc17a6a757
add afdf43e9d5a Upgrade apache pulsar 3.2.3 (#14270)
add 9741df9f423 Regen for commit afdf43e9d5a4f053c99506e1a3ce3bebabd27ffe
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 (5b4da92d917)
\
N -- N -- N refs/heads/regen_bot (9741df9f423)
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:
parent/pom.xml | 2 +-
.../org/apache/camel/test/infra/pulsar/services/container.properties | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
