This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch milvus-component
in repository https://gitbox.apache.org/repos/asf/camel.git
discard fbc913b478f CAMEL-20485 - Create a Camel-Milvus component
discard 5e5d2f9cfe0 CAMEL-20485 - Create a Camel-Milvus component - Full regen
discard 753990f151b CAMEL-20485 - Create a Camel-Milvus component - Added to
kit
discard 5dc67d98bf4 CAMEL-20485 - Create a Camel-Milvus component
discard 1f03298b4f1 CAMEL-20485 - Create a Camel-Milvus component
add fe2072468e2 Regen schema
add 9706c2a2aa8 Regen
add b4de13bee78 CAMEL-20485 - Create a Camel-Milvus component
add 10fcd9f3431 CAMEL-20485 - Create a Camel-Milvus component
add b255542aa83 CAMEL-20485 - Create a Camel-Milvus component - Added to
kit
add 13160f70435 CAMEL-20485 - Create a Camel-Milvus component - Full regen
add 17cefcaa915 CAMEL-20485 - Create a Camel-Milvus component
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 (fbc913b478f)
\
N -- N -- N refs/heads/milvus-component (17cefcaa915)
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:
