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.
omit 0fa7846 Regen for commit 2d95ec38d9ebe869f533d8c733dd0ee01fc014e2
add 07425d5 Regen for commit b060027d0fd3e56f609f10a40b9435e7b9e16ddd
add 8f3d512 Regen for commit 2d95ec38d9ebe869f533d8c733dd0ee01fc014e2
add 34f0fba Regen for commit 8f3d512374cbeeba6a6b9cd2b46c7a5961f1a982
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 (0fa7846)
\
N -- N -- N refs/heads/regen_bot (34f0fba)
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:
.../zookeeper/cloud/ZooKeeperServiceDiscoveryFactoryConfigurer.java | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
