You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by twcclegg <gi...@git.apache.org> on 2017/02/28 02:49:05 UTC
[GitHub] log4net pull request #42: LOG4NET-554 Use AsyncLocal for LogicalThreadContex...
GitHub user twcclegg opened a pull request:
https://github.com/apache/log4net/pull/42
LOG4NET-554 Use AsyncLocal for LogicalThreadContext
Replaces System.Runtime.Remoting.Messaging.CallContext which was removed in .NETStandard, with System.Threading.AsyncLocal which exists in .NET 4.6 and above
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/twcclegg/log4net-1 AsyncLocal4
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/log4net/pull/42.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #42
----
commit 53d435577890ef9a68b8929acead75301be9151a
Author: Thomas Clegg <tc...@godaddy.com>
Date: 2017-02-27T20:37:50Z
LOG4NET-554 Use AsyncLocal for LogicalThreadContext
commit cdcf231b028db599ff9f04705dc9ca1a0ecb17a0
Author: Thomas Clegg <tc...@godaddy.com>
Date: 2017-02-27T21:14:44Z
remove LogicalThreadContext from not supported list
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] log4net pull request #42: LOG4NET-554 Use AsyncLocal for LogicalThreadContex...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/log4net/pull/42
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---