This is an automated email from the ASF dual-hosted git repository.
nfilotto pushed a change to branch CAMEL-10173/component-etcd-v3
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 4d494837f5f CAMEL-10173: camel-etcd3 - Propose an async producer
omit a3665b1c571 CAMEL-10173: camel-etcd3 - Add an implementation based on
jetcd
omit 05a9e71d422 CAMEL-10173: camel-etcd3 - Add Test infra for etcd3
add 5fc9fbdb2e4 CAMEL-10173: camel-etcd3 - Add Test infra for etcd3
add 187e81566b4 CAMEL-10173: camel-etcd3 - Add an implementation based on
jetcd
add 0cf088fef37 CAMEL-10173: camel-etcd3 - Propose an async producer
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 (4d494837f5f)
\
N -- N -- N refs/heads/CAMEL-10173/component-etcd-v3
(0cf088fef37)
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:
test-infra/camel-test-infra-etcd3/pom.xml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
