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


 discard 86154df3f2a Regen for commit 5602d11fa4c324e82948c3b943c4aa8aaa3503b9
     add 4df86fac3f2 CAMEL-18125 fix multi node Kafka resume strategy empty 
cache
     add a1f2a072474 Regen for commit 4df86fac3f289bf07ef4908c2b1d1edb11d82224

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   (86154df3f2a)
            \
             N -- N -- N   refs/heads/regen_bot (a1f2a072474)

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:
 .../processor/resume/kafka/MultiNodeKafkaResumeStrategy.java  | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

Reply via email to