This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch camel-master
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git.
discard 6c91063 Fix cassandra for camel 3.5
discard 41d5d12 Regen
discard a5bfa92 Pointing the github actions to 3.5.0-SNAPSHOT
discard 5d85c31 Point to 3.5.0-SNAPSHOT
add ba1a288 GH Rebase action: no need for checking success
new ebbdccc Point to 3.5.0-SNAPSHOT
new 2c25a99 Pointing the github actions to 3.5.0-SNAPSHOT
new 0b51534 Regen
new 16ea8c8 Fix cassandra for camel 3.5
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 (6c91063)
\
N -- N -- N refs/heads/camel-master (16ea8c8)
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:
.github/workflows/rebase-master-onto-camel-master.yml | 3 ---
1 file changed, 3 deletions(-)
