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 5232de41 Minor: Regenerated License File for
6747acf4a406b1183953ca506a41f860ce02c7d3
add 65e5e478 Bump aws.version from 1.12.792 to 1.12.793 (#1711)
new 91f60c61 Minor: Regenerated License File for
65e5e47885a786added4b871e02cb1b4e640381c
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 (5232de41)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(91f60c61)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
THIRD-PARTY.txt | 10 +++++-----
external/aws/pom.xml | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
