This is an automated email from the ASF dual-hosted git repository.
FreeAndNil pushed a change to branch Feature/316-content-loss
in repository https://gitbox.apache.org/repos/asf/logging-log4net.git
omit 411f7b57 credit the fixer in every changelog entry
omit 60a3c7d8 stop the aspnet-request converter dropping events with
rejected content #316
omit 3273fc3a stop the ANSI terminal appender dropping empty messages #316
add 957cb26c stop the ANSI terminal appender dropping empty messages #316
add ebacb66b stop the aspnet-request converter dropping events with
rejected content #316
add 5b392b3d credit the fixer in every changelog entry
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 (411f7b57)
\
N -- N -- N refs/heads/Feature/316-content-loss (5b392b3d)
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:
