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 91cbfb9 Regen for commit cdb8d34220cf69d6eb532d98b06a0ab91a083c3c add 100238d CAMEL-16467 - Camel-Examples: Group the example for grouped componets in a middle folder add 776b495 CAMEL-16467 - Camel-Examples: Group the example for grouped componets in a middle folder add 38318a8 CAMEL-16467 - Camel-Examples: Group the example for grouped componets in a middle folder add 376f2f7 Regen for commit 38318a8ca8ffdafed3dfeefea1bfb29987555522 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 (91cbfb9) \ N -- N -- N refs/heads/regen_bot (376f2f7) 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: .../camel/maven/packaging/PrepareExampleMojo.java | 94 +++++++++++++--------- 1 file changed, 56 insertions(+), 38 deletions(-)