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 4a4b23217a4 Regen for commit 5c191c4189ef130be079439b9486c05705d6df43
add eda0fc5b02c Regen for commit 082fed0ac19f2a466d1376a2f60b964d0a402150
(#8282)
add 526e1e1afa8 CAMEL-18464: camel-jbang - upgrade to kamelets 0.9.0
add d0eb7e552a0 Regen for commit 526e1e1afa865d8acce95d9947f17f17155e03de
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 (4a4b23217a4)
\
N -- N -- N refs/heads/regen_bot (d0eb7e552a0)
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:
.../org/apache/camel/dsl/jbang/core/commands/ExportBaseCommand.java | 2 +-
dsl/camel-jbang/camel-jbang-main/dist/CamelJBang.java | 4 ++--
dsl/camel-jbang/camel-jbang-main/src/main/jbang/main/CamelJBang.java | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
