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 006ff4c Regen for commit a35c5ec526c53a985b4aec5a6820dc34cdfef684
add 2e0d5fd Upgrade Log4j to version 2.17.2
add 2ea18b7 Sync deps
add 58f2885 Regen for commit 2ea18b7ef1a2545e21a49ec275aa8ce14456674d
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 (006ff4c)
\
N -- N -- N refs/heads/regen_bot (58f2885)
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(-)
