This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch 20995-4.0.x
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 3bc5d0d9ad6 CAMEL-20995: azure-blob Enable retry during upload if
input stream support mark/reset
add d0e983eff36 Revert "CAMEL-20140: Fix camel-report:route-coverage to be
able to output coverage data (#12184)"
add 468b0a961cc CAMEL-20995: azure-blob Enable retry during upload if
input stream support mark/reset
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 (3bc5d0d9ad6)
\
N -- N -- N refs/heads/20995-4.0.x (468b0a961cc)
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:
.../java/org/apache/camel/parser/helper/RouteCoverageHelper.java | 5 ++++-
.../java/org/apache/camel/management/mbean/ManagedCamelContext.java | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
