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 c6576f0f3c2 Regen for commit 416fa2351b3a7038294918d8d73dc22d605c05d9
add d61b1bb4615 CAMEL-19128: camel-jbang - Set version command
add a2172360ede Regen for commit d61b1bb4615f662e9957c0f51d96f89da1cbb96e
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 (c6576f0f3c2)
\
N -- N -- N refs/heads/regen_bot (a2172360ede)
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:
.../dsl/jbang/core/commands/CamelJBangMain.java | 2 +
.../version/{VersionGet.java => VersionSet.java} | 49 +++++++++++++---------
2 files changed, 32 insertions(+), 19 deletions(-)
copy
dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/version/{VersionGet.java
=> VersionSet.java} (50%)
