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 2ee3620 Regen for commit 17ea6cc8942571dc2853bf40699092be3c41c9ee
add 9d93633 Upgrade ArangoDB to version 6.8.0
add 2739bb4 Sync deps
add 4afa45f Regen for commit 2739bb4f8d07e796db7a4f21caeb85206e665972
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 (2ee3620)
\
N -- N -- N refs/heads/regen_bot (4afa45f)
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(-)
