| commit | 4dd4398384124f9affe74b18433e10f3de4fdf23 | [log] [tgz] |
|---|---|---|
| author | Robert Middleton <rm5248@users.noreply.github.com> | Mon Aug 30 15:51:36 2021 -0700 |
| committer | GitHub <noreply@github.com> | Mon Aug 30 18:51:36 2021 -0400 |
| tree | e56cf16d0a8d19a22b086fab59a86351e29d2bf0 | |
| parent | 5cf7c9a5b3d4f02c45ef5b12707b6c5431a557a0 [diff] |
LOGCXX-431 (#68) * LOGCXX-431 Update thread creation In order to make it possible to block signals when a thread is created, a new API to let users configure what to do when a thread is started has been created. Documentation on how Log4cxx handles threads, and information about good ways to handle signals has been added as well. Note that this does not automatically configure signals to be blocked by default on POSIX systems. This is intended to be the default shortly.
Issues are maintained in the Apache JIRA by default, so before posting pull requests, please have a look there if an associated issue with your problem/feature/... exists already. If not, it‘s generally OK to directly create pull requests IF code is already available, but please be somewhat verbose: Provide some background information about what actual problem the PR solves, why this needs to be solved etc. Don’t just provide commits about the fact that you changed something.
If any discussion is needed before actually having any code, simply create a ticket in JIRA or send a message to the corresponding mailing list. Thanks!