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 d32e8713e55 Regen for commit f7f3ed0c10e757cca1bfdd2fd2f6a0140745b1bd
     add 2d24ae744ae Regen for commit f7f3ed0c10e757cca1bfdd2fd2f6a0140745b1bd
     add ffd382b1b48 Regen for commit e9a7a1c46b43a101a8faccda787aa7fcf75f6235

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   (d32e8713e55)
            \
             N -- N -- N   refs/heads/regen_bot (ffd382b1b48)

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/catalog/schemas/camel-spring.xsd  | 7936 +++++++++++++-------
 1 file changed, 5363 insertions(+), 2573 deletions(-)

Reply via email to