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 0164b223e09 Regen for commit 89bad05f66f1303d24d5a8d64c6b0dae90e659a6
add e4671271949 [CAMEL-18285] Lazy-loading for file length and last
modified attributes (#8019)
add d39baf836cd Regen for commit 4f61ec1cb728f22b1e96c51bbd3665e7549ce91a
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 (0164b223e09)
\
N -- N -- N refs/heads/regen_bot (d39baf836cd)
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/file/FileConsumer.java | 6 ++++--
.../apache/camel/component/file/GenericFile.java | 21 +++++++++++++++++++++
2 files changed, 25 insertions(+), 2 deletions(-)
