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
discard b4a70d4e289 Regen for commit 0941aabb32b058225d712389fc2b477730a3cba5
add 35b16aed25a (chores) camel-mllp: parallelize unit tests
add b3ea68530a7 Regen for commit 35b16aed25a6ec19224a619f84c7e7089d14d2d8
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 (b4a70d4e289)
\
N -- N -- N refs/heads/regen_bot (b3ea68530a7)
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:
components/camel-mllp/pom.xml | 5 +++++
.../camel/component/mllp/internal/MllpSocketBufferWriteTest.java | 2 ++
2 files changed, 7 insertions(+)
