This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch
regenerate_notice_file_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/opennlp.git
discard 39ee073de Minor: Regenerated NOTICE File for
12b7b196cf434cecbf7ad87b5a57dea4c6324e48
add d7e17cef1 OPENNLP-1824: Update ONNX runtime to 1.26.0 (#1046)
add c70872fd5 Minor: Regenerated NOTICE File for
d7e17cef170ee9910594ff0e689e70b97f2018bd
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 (39ee073de)
\
N -- N -- N refs/heads/regenerate_notice_file_after_dep_upgrade
(c70872fd5)
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 | 4 ++--
opennlp-distr/src/main/readme/NOTICE | 4 ++--
pom.xml | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
