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 e256b0def2f Regen for commit 3c011c9cc2e6d1ba986dadb13e8a5a6c77f7736c
add 5cb3b82ad86 Regen for commit ab6b232c897b8a6bc1aaa3310f0400e39e7d3095
add 5ce91c65952 (chores) camel-mllp: disabled flaky test on Github
add 40bc656bf74 Regen for commit 5ce91c65952eaee0171b70397cf74ab88d343f34
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 (e256b0def2f)
\
N -- N -- N refs/heads/regen_bot (40bc656bf74)
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:
.../MllpTcpClientProducerConnectionErrorTest.java | 2 ++
.../endpoint/dsl/PulsarEndpointBuilderFactory.java | 33 ++++++++++++++++++++++
2 files changed, 35 insertions(+)
