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 35fc64aea09 Regen for commit 369572877d3b65547da6de9dda126d06ab0341a3
add 69d6b57fb63 Regen for commit 8199b336d5f8c9ac87fc6abca8b18be29cacc017
(#8224)
add f09b275b3f6 CAMEL-18425: camel-cli - Make regular Camel applications
work with Camel CLI
add e0be6380dae Regen for commit f09b275b3f62599eef53f75d6145849bead7c89a
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 (35fc64aea09)
\
N -- N -- N refs/heads/regen_bot (e0be6380dae)
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:
.../core/commands/process/ProcessBaseCommand.java | 24 ++++++++++++++--------
1 file changed, 15 insertions(+), 9 deletions(-)
