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 77eebf53318 Regen for commit 058c0b7e116c8d9457064b01e1581fd0047866ec
add 74c05f3c0dc [camel-resilience4j] Increase test coverage making a
context pooled (#8799)
add 97fb9229c2f Regen for commit 74c05f3c0dc2f5b71413d555562ab84eda90b15e
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 (77eebf53318)
\
N -- N -- N refs/heads/regen_bot (97fb9229c2f)
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:
.../{ResilienceRouteOkTest.java => ResiliencePooledRouteOkTest.java} | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
copy
components/camel-resilience4j/src/test/java/org/apache/camel/component/resilience4j/{ResilienceRouteOkTest.java
=> ResiliencePooledRouteOkTest.java} (93%)
