This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git.
discard 2c7783f Regen for commit 78385aa5b90aa74ac7dbe94316db34699934fb7d
add f1280bd CAMEL-16627: camel-core - Add common header for source
timestamp
add 0d9d49e CAMEL-16627: camel-core - Add common header for source
timestamp
add 92add4c Regen for commit 5723a25f6253f8012b9d9dd23e5b0c4babb2f28e
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 (2c7783f)
\
N -- N -- N refs/heads/regen_bot (92add4c)
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:
.../org/apache/camel/component/azure/eventhubs/EventHubsConsumer.java | 4 ++++
.../camel/component/azure/storage/blob/BlobExchangeHeaders.java | 4 ++++
.../component/azure/storage/datalake/DataLakeExchangeHeaders.java | 4 ++++
.../camel/component/azure/storage/queue/QueueExchangeHeaders.java | 4 ++++
.../java/org/apache/camel/component/debezium/DebeziumEndpoint.java | 1 +
5 files changed, 17 insertions(+)
