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
discard 2c9d8312b9 Remove reflection from `log4j-to-jul` and `log4j-to-slf4j`
discard 45c7ccf05e Port `Tags` from 3.x
discard 2bcfce910d Make default message factories GraalVM friendly
discard 54517c0a63 Add `Strings#trimToOptional`
discard a0ee40cef6 Remove deprecations from functional interfaces
discard 3fe2f98e6b Adapt `ReusableMessage` to be used in 3.x
discard 2fc0c47331 Simplify `ServiceLoaderUtil`
add d1419e6ebb Simplify `ServiceLoaderUtil`
add 0d81a75434 Adapt `ReusableMessage` to be used in 3.x
add 7998c9b791 Remove deprecations from functional interfaces
add 74029a6f09 Add `Strings#trimToOptional`
add bff0bf296b Make default message factories GraalVM friendly
add 500ecb7c6e Port `Tags` from 3.x
add 09821aab46 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 (2c9d8312b9)
\
N -- N -- N refs/heads/fix/backport-log4j3-api (09821aab46)
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-api/pom.xml | 4 ++++
.../src/main/java/org/apache/logging/log4j/util/StackLocator.java | 3 ++-
2 files changed, 6 insertions(+), 1 deletion(-)
