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 e7cb2c9 Regen for commit a7071b3093e7593aad8e59006b9933cee13cebff
add 0655c09 CAMEL-14871 - Regen docs, configurers and DSLs
add 8a9c507 (chores) camel-test-junit5: cleanups (#4957)
add 6f383a4 Regen for commit 8a9c50749dc4dc63467179f0df28340f91c5ed1c
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 (e7cb2c9)
\
N -- N -- N refs/heads/regen_bot (6f383a4)
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:
.../apache/camel/test/junit5/CamelTestSupport.java | 48 ++++++++++------------
1 file changed, 22 insertions(+), 26 deletions(-)
