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_2.x
in repository https://gitbox.apache.org/repos/asf/opennlp.git


 discard 99078f3cf Minor: Regenerated NOTICE File for 
0e287c8f6b76ac105a6cdad76473aa5665d93bd6
     add ae68da54d [2.x]: OPENNLP-1827 Update log4j2 to 2.26.0 (#1036)
     add a2d631e26 Minor: Regenerated NOTICE File for 
ae68da54da53b4803cdade86ba7c3a8ef7c28bd5

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   (99078f3cf)
            \
             N -- N -- N   
refs/heads/regenerate_notice_file_after_dep_upgrade_2.x (a2d631e26)

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 +++---
 opennlp-distr/src/main/readme/NOTICE | 6 +++---
 pom.xml                              | 2 +-
 3 files changed, 7 insertions(+), 7 deletions(-)

Reply via email to