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 182cb62 Regen for commit 20bf274946fecf2da9791ddd55ee5d136c3ec05b
omit 20bf274 CAMEL-17258 - added support for changing length of tracing
groups
add f904427 Regen for commit 3af40ea87ebf9a343538149e2652cb0a8bddcbf6
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 (182cb62)
\
N -- N -- N refs/heads/regen_bot (f904427)
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/tracer.adoc | 48 +++++--------------------
1 file changed, 8 insertions(+), 40 deletions(-)
