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

jamesnetherton pushed a change to branch camel-master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.


 discard 4540f90  Invoke getExitCode from CamelMain
 discard 4fbcca3  Fix infinispan extension and clean up redundant substitutions
 discard d3ad794  Regen docs
 discard 38e3947  add HazelcastReplicatedmapConsumer test fixes #2095
 discard 528a996  Allow to reset build taken for native builds that are super 
fast.
 discard d5b397a  Adjust to camel 3.8 change
 discard 84b994b  Upgrade to Camel 3.8.0
     new 576f327  Upgrade to Camel 3.8.0
     new 52b52b4  Allow to reset build taken for native builds that are super 
fast.
     new c06756f  add HazelcastReplicatedmapConsumer test fixes #2095

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   (4540f90)
            \
             N -- N -- N   refs/heads/camel-master (c06756f)

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.

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../camel/quarkus/core/DisabledXMLRoutesDefinitionLoader.java       | 6 ------
 1 file changed, 6 deletions(-)

Reply via email to