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/opennlp.git
discard c1d12fba Minor: Regenerated NOTICE File for
ecabec472cabbee1394806bc891b696e52cf35f2
add 65b1f8c3 OPENNLP-1772: Update log4j2 to 2.25.2 (#855)
add b7e33ed1 Minor: Regenerated NOTICE File for
65b1f8c31b5fb0b861b4c4e47bb9b284d3c64039
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 (c1d12fba)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(b7e33ed1)
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:
NOTICE | 6 +++---
pom.xml | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)