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.
discard 834858a Regen for commit 3a24dff5b048892c01156e177a23535ca440de98
add 3f7aea3 Upgrade Jedis to version 3.5.1
add 68bb67c Sync deps
add 8340602 Regen for commit 68bb67c1acddc22baebaffa8a5d45a02eb0b55de
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 (834858a)
\
N -- N -- N refs/heads/regen_bot (8340602)
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(-)
