This is an automated email from the ASF dual-hosted git repository.
ppkarwasz pushed a change to branch feat/2.x/log-event-proxy-wrapped-message
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
discard 3b05d049ea Serialize the LogEvent message delegate through the
filtered wrapper
add 3df4199d11 Serialize the LogEvent message delegate through the
filtered wrapper
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 (3b05d049ea)
\
N -- N -- N refs/heads/feat/2.x/log-event-proxy-wrapped-message
(3df4199d11)
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:
...ml => 4271_remove_marshalled_object_from_log_event_serialization.xml} | 1 +
1 file changed, 1 insertion(+)
rename
src/changelog/.2.x.x/{remove_marshalled_object_from_log_event_serialization.xml
=> 4271_remove_marshalled_object_from_log_event_serialization.xml} (85%)
