You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/10/25 09:57:00 UTC
[jira] [Work logged] (LOG4NET-630) Log4Net missing Timestamp etc.
in internal LogLog
[ https://issues.apache.org/jira/browse/LOG4NET-630?focusedWorklogId=669425&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-669425 ]
ASF GitHub Bot logged work on LOG4NET-630:
------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Oct/21 09:56
Start Date: 25/Oct/21 09:56
Worklog Time Spent: 10m
Work Description: fluffynuts commented on pull request #49:
URL: https://github.com/apache/logging-log4net/pull/49#issuecomment-950742297
Good day
It's been quite a while since this PR last saw activity. In an attempt to get pull requests under some semblance of
order, I'm having to make the uncomfortable decision to jettison pull requests which have been dormant for quite some
time. Perhaps arbitrarily, I'm choosing all pull requests which have not seen activity this year (2021), most of
which are marked as not building or have conflicts with the main branch.
This is _not_ because the contributions aren't valuable - it's simply a matter of being the only person spending
some time on this and being a little overwhelmed. I'd rather get some traction on newer issues than continue
to try to understand, upgrade and work through PRs which don't build or which conflict with the main branch,
or which simply may have been solved in the mean time.
I encourage you to re-submit the PR against the current main branch if the issue is still significant. Your
contributions are appreciated. I apologise for any inconvenience caused and sincerely hope that you understand
the constraints involved which have brought me to the place of making this decision.
--
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 to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 669425)
Time Spent: 1h 40m (was: 1.5h)
> Log4Net missing Timestamp etc. in internal LogLog
> -------------------------------------------------
>
> Key: LOG4NET-630
> URL: https://issues.apache.org/jira/browse/LOG4NET-630
> Project: Log4net
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.8
> Reporter: Miro Jablonsky
> Priority: Minor
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> I am facing the same problem as described in following StackOverflow topic: [Log4Net internal debug Timestamp|https://stackoverflow.com/questions/40077917/log4net-internal-debug-timestamp]
> Citation:
> I am having intermittent problems with Log4net not logging and in other threads there is a suggestion to setup internal logging by
> <add key="{color:#d04437}log4net.Internal.Debug{color}" value="{color:#d04437}true{color}"/>
> I have added this and it does work, which is great, but there is no timestamp. Is there a way I can have Timestamp on the internal logging. Any help is appreciated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)