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 f2a9d265250 Regen for commit aa377059572d528e421c84b031a21830416a81a1
add f51d44a8e04 Upgrade Azure SDK BOM to version 1.2.9
add c61fb74a8d2 Sync deps
add 9734da7cd4d Regen for commit c61fb74a8d2657609d8f98da318d4bec639d53ea
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 (f2a9d265250)
\
N -- N -- N refs/heads/regen_bot (9734da7cd4d)
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-dependencies/pom.xml | 2 +-
parent/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
