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 76571b66959 Regen for commit b09eb5761504d34df8e5bad836a91e3a9dab799a
add ac50db58ac9 (chores) camel-ftp: minor FtpConsumer cleanup
add 6090512ceb5 Regen for commit ac50db58ac928b6a8c8924d3153cec0c483e60d8
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 (76571b66959)
\
N -- N -- N refs/heads/regen_bot (6090512ceb5)
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/component/file/remote/FtpConsumer.java | 97 ++++++++++++++--------
1 file changed, 61 insertions(+), 36 deletions(-)
