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

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


 discard 8f9336b  HBase integration tests fail with Camel 3.6.0 Fix #1914
 discard 494e006  Enable Camel 3.6.0 staging repository temporarily
 discard 9776595  Improve the camel-bean extension by not using an alias for 
BeanAnnotationExpressionFactory #1725
 discard 0f081d9  Remove workaround for CAMEL-15518 #1769
 discard 398dd51  Remove HipChat after it was removed from Camel 3.6.0
     new 3db1bb3  Remove HipChat after it was removed from Camel 3.6.0
     new 8349c6e  Remove workaround for CAMEL-15518 #1769
     new 96f1c0a  Improve the camel-bean extension by not using an alias for 
BeanAnnotationExpressionFactory #1725
     new 13c89fb  Enable Camel 3.6.0 staging repository temporarily
     new 0f246b2  HBase integration tests fail with Camel 3.6.0 Fix #1914

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   (8f9336b)
            \
             N -- N -- N   refs/heads/release/1.3.0 (0f246b2)

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 5 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:
 docs/modules/ROOT/nav.adoc | 1 -
 1 file changed, 1 deletion(-)

Reply via email to