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 95685a2018a Regen for commit eb0acef79b59e12843bef08c27cd3a352ccd2a42
add 5786f4f72f3 CAMEL-9627: Regen
add d9e56a80382 (chores) camel-jms: renamed manual test
add d0248b22559 Regen for commit d9e56a8038284759b1706bfb12b0a8705afc5f9a
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 (95685a2018a)
\
N -- N -- N refs/heads/regen_bot (d0248b22559)
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:
.../temp/{JmsReconnectTest.java => JmsReconnectManualTest.java} | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
rename
components/camel-jms/src/test/java/org/apache/camel/component/jms/temp/{JmsReconnectTest.java
=> JmsReconnectManualTest.java} (95%)
