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 4d13c8ab4bf Regen for commit c897bb0b72fa825a622ef5224c47a48ca8692a4c
add cd2cae3b899 CAMEL-19062 - Clean up Parent POM - Fastjson
add bf33e5bcb0c CAMEL-19033: camel-jbang - get trace -> trace
add e5fe7c93cd2 Regen for commit bf33e5bcb0c82b7c1f195969b5b33cbeec58b3c0
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 (4d13c8ab4bf)
\
N -- N -- N refs/heads/regen_bot (e5fe7c93cd2)
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:
components/camel-fastjson/pom.xml | 3 ++-
.../camel/dsl/jbang/core/commands/action/CamelTraceAction.java | 2 +-
parent/pom.xml | 6 ------
3 files changed, 3 insertions(+), 8 deletions(-)
