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

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


 discard ec44edb  CSimple language support #2036
 discard ac39f03  Remove Camel AS2 configuration class reflection registration
 discard 1839582  BigQuery native support
 discard aef9ea8  Google PubSub native support
 discard bfd1833  [Camel 3.7] JSON-B data format support
 discard 5b86976  Upgrade to Camel 3.7.0
     new 707d828  Upgrade to Camel 3.7.0
     new 89aa67f  [Camel 3.7] JSON-B data format support
     new c1817ff  Google PubSub native support
     new c606e9b  BigQuery native support
     new 3be56b4  Remove Camel AS2 configuration class reflection registration
     new 1fb2169  CSimple language support #2036

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   (ec44edb)
            \
             N -- N -- N   refs/heads/camel-master (1fb2169)

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 6 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/partials/reference/others/{zipkin.adoc => elytron.adoc} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 copy docs/modules/ROOT/partials/reference/others/{zipkin.adoc => elytron.adoc} 
(100%)

Reply via email to