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 fd3062ca08a Regen for commit 6ff720a24cf648ba09b76bab6568ec6c97dc5df1
add 2c60e09391d Update try-catch-finally.adoc (#8974)
add b2f4ce3e3ce Regen for commit 2c60e09391da75956f0eda46a823bed958ec8f79
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 (fd3062ca08a)
\
N -- N -- N refs/heads/regen_bot (b2f4ce3e3ce)
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:
docs/user-manual/modules/ROOT/pages/try-catch-finally.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)