This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a change to branch fix/CAMEL-23877
in repository https://gitbox.apache.org/repos/asf/camel.git


 discard fecf25611335 CAMEL-23877: Fix camel-pinecone tls option documented 
default and add insecure:ssl annotation
     add d03b07c13b89 CAMEL-24003: Fix BacklogTracerActivityTest to enable 
activity before sending messages
     add b90ff37fbf0d CAMEL-23877: Fix camel-pinecone tls option documented 
default and add insecure:ssl annotation

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   (fecf25611335)
            \
             N -- N -- N   refs/heads/fix/CAMEL-23877 (b90ff37fbf0d)

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:
 .../org/apache/camel/management/BacklogTracerActivityTest.java   | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

Reply via email to