This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_license_file_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/stormcrawler.git
omit 1ed14ee1 Minor: Regenerated License File for
64028dc44d532fe80dbe6e13ce14fadeb63e7e07
add ba5d39f8 Bump aws.version from 1.12.796 to 1.12.797 (#1772)
add 6036714f Minor: Regenerated License File for
ba5d39f8afc2ba20dd4c04d67ff035b07a1d8789
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 (1ed14ee1)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(6036714f)
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:
THIRD-PARTY.txt | 10 +++++-----
external/aws/pom.xml | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
