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 e3a22bf0cc2 Regen for commit 894a526ba8debbfe429850879abd5757ec402d04 add 72fbfd26664 Regen for commit 894a526ba8debbfe429850879abd5757ec402d04 (#10616) add c9d6ce6d1f5 Regen for commit 72fbfd266644f37966f5d8cac7a3936dff0113d6 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 (e3a22bf0cc2) \ N -- N -- N refs/heads/regen_bot (c9d6ce6d1f5) 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: .../resources/org/apache/camel/catalog/schemas/camel-spring.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)