travisspencer commented on pull request #578:
URL: https://github.com/apache/logging-log4j2/pull/578#issuecomment-915786974
Great. Thanks, @carterkozak .
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above t
jeff created LOG4NET-674:
Summary: Document how to add custom levels to log4net repository
Key: LOG4NET-674
URL: https://issues.apache.org/jira/browse/LOG4NET-674
Project: Log4net
Issue Type: Improve
carterkozak commented on pull request #578:
URL: https://github.com/apache/logging-log4j2/pull/578#issuecomment-915521576
When I merge changes I cherry-pick them to the other branch, no need to
create additional PRs since it tends to split the discussion. We add changelog
entries for most
travisspencer commented on pull request #578:
URL: https://github.com/apache/logging-log4j2/pull/578#issuecomment-915515500
Ah, good to know. Would it help at all if I cherry-pick it to that branch
and make a separate PR or do commits to the main line get back-ported
automatically somehow?
carterkozak commented on pull request #578:
URL: https://github.com/apache/logging-log4j2/pull/578#issuecomment-915504002
It works best if you target the release-2.x branch
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
travisspencer commented on pull request #578:
URL: https://github.com/apache/logging-log4j2/pull/578#issuecomment-915501455
Thanks, @carterkozak , for accepting this fix. Do you know if I can get a
build of this off the CI server somehow? I need the fix to test some other
stuff, and I'm no
rm5248 opened a new pull request #70:
URL: https://github.com/apache/logging-log4cxx/pull/70
As requested in LOGCXX-431 by @coldtobi, the new thread configuration blocks
signals on POSIX by default.
A new option for the configuration files has also been added, so that you
may config
