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 1663d91eddc Regen for commit ed7c813f2b7e6eff4cffcae036f1c694621271d3
add b1a6b8bff6d Regen for commit e40d835eb6d8456ab07af5f9fa489aaa204ac494
add 8db9d8fb48f CAMEL-18267: ContextReloadStrategy to reload all routes
after external changes such as properties/vault updated.
add 4edfd6e9dff Regen for commit 8db9d8fb48fde943c79c72571c9b5494c7975e6b
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 (1663d91eddc)
\
N -- N -- N refs/heads/regen_bot (4edfd6e9dff)
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:
.../camel/impl/console/ContextDevConsole.java | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
