This is an automated email from the ASF dual-hosted git repository.
vy pushed a change to branch release/2.25.3
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
discard b4079d68c6 Get ready for the `2.25.3` release
discard 4bfb155da2 Fix log message in `ApiLogger::setUseParentHandlers` (#3943)
discard 28f8f392cc Fix nullability issues in `SslConfiguration` (#3953)
discard 0bc96f1dca Remove the `com.github.spotbugs:spotbugs-annotations`
dependency (#3984, #3985)
new 8d43a991c3 Remove the `com.github.spotbugs:spotbugs-annotations`
dependency (#3984, #3985)
new 6076b1639a Fix nullability issues in `SslConfiguration` (#3953)
new 73db4fb4d9 Fix log message in `ApiLogger::setUseParentHandlers` (#3943)
new 041435dada Get ready for the `2.25.3` release
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 (b4079d68c6)
\
N -- N -- N refs/heads/release/2.25.3 (041435dada)
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 4 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:
.../org/apache/logging/log4j/core/appender/MemoryMappedFileManager.java | 2 +-
.../org/apache/logging/log4j/core/appender/RandomAccessFileManager.java | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
