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 eb57808096e Regen for commit 731f6dfd754d80e4435f1843673763954ac09fa9
     add 4eaa87f8c90 camel-yaml-dsl - Added unit test
     add de990047ece camel-core - Fix backlog tracer captuing source location 
for route input
     add 451363453d4 Regen for commit de990047ecefeed3ad6a7e613a9b48613295cd1a

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   (eb57808096e)
            \
             N -- N -- N   refs/heads/regen_bot (451363453d4)

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:
 .../camel/impl/engine/CamelInternalProcessor.java  |  4 +++-
 .../yaml/{LogTest.groovy => LocationTest.groovy}   | 24 ++++++++++++----------
 2 files changed, 16 insertions(+), 12 deletions(-)
 copy 
dsl/camel-yaml-dsl/camel-yaml-dsl/src/test/groovy/org/apache/camel/dsl/yaml/{LogTest.groovy
 => LocationTest.groovy} (74%)

Reply via email to