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 26fce096033 Regen for commit 425293d0291328f50304f51029a8e60422bb52df
add db676c0ae68 CAMEL-18497: camel-jbang - Run command now supports
specifying a different Camel version.
add 35a4a058902 Regen for commit db676c0ae68cfad10fbd47ea0b936f483f9c99b0
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 (26fce096033)
\
N -- N -- N refs/heads/regen_bot (35a4a058902)
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:
.../src/main/java/org/apache/camel/dsl/jbang/core/commands/Run.java | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
