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 b28841c24f7 Regen for commit 04ea1633ae2b5146f74160916f38e8b0e0018664 add 9c1a13517a5 (chores) camel-aws2-athena: avoid shadowing member variables add ba422717c59 (chores) camel-facebook: avoid unnecessary object instantiation add 09bbb778b17 (chores) camel-aws2-sts: avoid shadowing member variables add a9e493bbc34 (chores) camel-base-engine: avoid unnecessary object instantiation add b39d37b467c Regen for commit a9e493bbc3455b289e6f69a2d7aee28ef786a29c 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 (b28841c24f7) \ N -- N -- N refs/heads/regen_bot (b39d37b467c) 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: .../apache/camel/component/aws2/athena/Athena2Component.java | 10 +++++----- .../org/apache/camel/component/aws2/sts/STS2Component.java | 8 ++++---- .../camel/component/facebook/data/FacebookMethodsType.java | 6 +++--- .../org/apache/camel/impl/engine/CamelInternalProcessor.java | 3 +-- 4 files changed, 13 insertions(+), 14 deletions(-)