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

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


 discard 19371f939f65 CAMEL-22742: camel-core - Rest DSL contract first should 
have jmx statistics
 discard f90e3979dd70 CAMEL-22742: camel-core - Rest DSL contract first should 
have jmx statistics
 discard 9ec00974ff12 CAMEL-22742: camel-core - Rest DSL contract first should 
have jmx statistics
 discard 068c9c829a52 rest-dsl using contract-first should include source 
location for pseudo-route
 discard b687ba43bfed Fixed potential NPE in camel-jbang
     add 6f20b5305681 rest-dsl using contract-first should include source 
location for pseudo-route
     add 7fb9d34e67dd CAMEL-22742: camel-core - Rest DSL contract first should 
have jmx statistics
     add cb4f1fbb5876 CAMEL-22742: camel-core - Rest DSL contract first should 
have jmx statistics
     add bddb2c740321 CAMEL-22742: camel-core - Rest DSL contract first should 
have jmx statistics

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   (19371f939f65)
            \
             N -- N -- N   refs/heads/rest-jmx (bddb2c740321)

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:

Reply via email to