This is an automated email from the ASF dual-hosted git repository.
pkarwasz pushed a change to branch feature/move-thread-context
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
discard 8a43fa3bbb Merge remote-tracking branch 'refs/remotes/apache/2.x' into
feature/move-thread-context
discard 33ba51e2dc Fix MDC configuration documentation
discard 50f6c36fc1 Deprecate `CopyOnWrite` interface
discard 172e319309 Apply suggestions from code review
discard 8d4f3414ca Fix Javadoc
discard 5e2d0ca2bd Reverse search order in `ThreadContextMap#remove()`
discard 392e19391e Fix OSGi tests
discard fc51ccdbce Update documentation
discard db7df886ac Use `loadThreadContextMap` in default
`getThreadContextMapInstance()`
discard b442693772 Move `GarbageFreeSortedArrayThreadContextMap` to
`log4j-core`
discard 437dcd6aa2 Remove `CopyOnWriteSortedArrayThreadContextMap`
discard b2ddfc8f33 Make `StringArray` the default thread context map
add f27f6bce68 Clean up `ThreadContextMap` implementations
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 (8a43fa3bbb)
\
N -- N -- N refs/heads/feature/move-thread-context (f27f6bce68)
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:
