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 7b0fd8a nats: Raised the TLS handshake timeout to fix builds when O/S
is under pressure #1978
discard 0132613 [Camel 3.7] JSON-B data format support
discard b576eaa nats: enabled connections fine grained tracing to capture
more information on next occurence of issue #1978
discard e9153d8 Upgrade to Camel 3.7.0
new 0dd2c0d Upgrade to Camel 3.7.0
new 40334d1 nats: enabled connections fine grained tracing to capture
more information on next occurence of issue #1978
new ea88485 [Camel 3.7] JSON-B data format support
new ed930b0 nats: Raised the TLS handshake timeout to fix builds when O/S
is under pressure #1978
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 (7b0fd8a)
\
N -- N -- N refs/heads/camel-master (ed930b0)
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 4 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:
extensions-support/spring/core/pom.xml | 1 +
1 file changed, 1 insertion(+)
