This is an automated email from the ASF dual-hosted git repository.
pkarwasz pushed a change to branch fix/backport-log4j3-api
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
omit 8882b25232 Remove reflection from `log4j-to-jul` and `log4j-to-slf4j`
omit 9ba858c3e3 Port `Tags` from 3.x
omit 16f16d98a8 Make default message factories GraalVM friendly
omit 5bd7a760f4 Add `Strings#trimToOptional`
omit 079a237666 Remove deprecations from functional interfaces
omit 486289cfd3 Adapt `ReusableMessage` to be used in 3.x
omit b755ffe6cf Simplify `ServiceLoaderUtil`
add 2fc0c47331 Simplify `ServiceLoaderUtil`
add 3fe2f98e6b Adapt `ReusableMessage` to be used in 3.x
add a0ee40cef6 Remove deprecations from functional interfaces
add 54517c0a63 Add `Strings#trimToOptional`
add 2bcfce910d Make default message factories GraalVM friendly
add 45c7ccf05e Port `Tags` from 3.x
add 2c9d8312b9 Remove reflection from `log4j-to-jul` and `log4j-to-slf4j`
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 (8882b25232)
\
N -- N -- N refs/heads/fix/backport-log4j3-api (2c9d8312b9)
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:
.../src/main/java/org/apache/logging/log4j/test/junit/package-info.java | 2 +-
.../src/main/java/org/apache/logging/log4j/tojul/package-info.java | 2 +-
log4j-to-slf4j/src/main/java/org/apache/logging/slf4j/package-info.java | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
