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 296ffd4bbb4 Regen for commit da17f7093ff6359b3c2db55544491e3cd758c3d8
add 50281fd015c Regen for commit 7af3fa63f58d67079b2975917b092e532c2b98bc
add 366f886246b Upgrade impsort maven plugin
add 1be24408de4 (chores) camel-jms: fixed build due to incorrect regen
add 2d663fe01ea Regen for commit 1be24408de478d282afddb370cf7fc3b341df9c6
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 (296ffd4bbb4)
\
N -- N -- N refs/heads/regen_bot (2d663fe01ea)
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(-)
