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 1ae414bb971 Regen for commit 80c4d89d62455b71d8432110f6103ae5c367f93b
add 24e17a0623d Regen for commit dc9ebe6dd1d1e73619dfd1ede2d7bc4e11afa16a
add ae31f4006dc CAMEL-18118: camel-jbang - Linux terminal scripting using
pipes
add 2d6ed042c68 Regen for commit ae31f4006dc4833b7d7968ea9f19f7d067bda56d
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 (1ae414bb971)
\
N -- N -- N refs/heads/regen_bot (2d6ed042c68)
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:
.../java/org/apache/camel/dsl/support/RouteBuilderLoaderSupport.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
