Github user StrangeWill commented on the pull request:
https://github.com/apache/log4net/pull/16
@bodewig _Hopefully_ there shouldn't be much flux between RC2 and Final
(well at least we were told porting from RC2 -> Final won't be nearly as bad as
RC1 -> RC2 was, and it wasn't
Github user bodewig commented on the pull request:
https://github.com/apache/log4net/pull/16#issuecomment-222350005
Please note I'm just one voice others may think differently about this.
Given the amount of flux that's going on I'm a bit reluctant to adapt to .NET
Core before 1.0 is
Github user chlowell commented on the pull request:
https://github.com/apache/log4net/pull/16#issuecomment-222199688
I have another branch on my fork (`dotnetcore-rc2`) which builds with RC2
tools, and has some improvements over the code here. A few tests are broken due
to executing
Github user chester89 commented on the pull request:
https://github.com/apache/log4net/pull/16#issuecomment-222102483
@chlowell any updates on this?
---
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
Github user bodewig commented on the pull request:
https://github.com/apache/log4net/pull/16#issuecomment-163839682
referenced in LOG4NET-467 https://issues.apache.org/jira/browse/LOG4NET-467
---
If your project is set up for it, you can reply to this email and have your
reply appear
