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 4c1120c8 cite the audit findings behind the Ext.Mail and syslog work
#314
omit 892cded8 credit the fixer in every changelog entry
omit 8b44780a stop the aspnet-request converter dropping events with
rejected content #316
omit da4b4af5 stop the ANSI terminal appender dropping empty messages #316
add 5a37f178 Merge pull request #315 from
apache/Feature/315-local-syslog-newlines
new d3b8e9b9 stop the ANSI terminal appender dropping empty messages #316
new 14520342 stop the aspnet-request converter dropping events with
rejected content #316
new 39033a49 credit the fixer in every changelog entry
new 7de84b7d cite the audit findings behind the Ext.Mail and syslog work
#314
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 (4c1120c8)
\
N -- N -- N refs/heads/Feature/316-content-loss (7de84b7d)
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.
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
