This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/2.x/org.jmdns-jmdns-3.5.12
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
discard 4d61528260 Bump org.jmdns:jmdns from 3.5.11 to 3.5.12
add 6d74d4bbf7 Update `de.flapdoodle.reverse:de.flapdoodle.reverse` to
version `1.8.0` (#2881)
add 67848c1fc2 Update `org.jmdns:jmdns` to version `3.5.12` (#2879)
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 (4d61528260)
\
N -- N -- N
refs/heads/dependabot/maven/2.x/org.jmdns-jmdns-3.5.12 (67848c1fc2)
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:
log4j-parent/pom.xml | 2 +-
.../.2.x.x/update_de_flapdoodle_reverse_de_flapdoodle_reverse.xml | 4 ++--
src/changelog/.2.x.x/update_org_jmdns_jmdns.xml | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
